SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello. I want to update mesa to take advantage of some features in wine-staging. I download the newest version of mesa and run ./configure. The process ends at this:
Code:
configure: error: Direct rendering requires libdrm >= 2.4.60
So then I downloaded libdrm-2.4.65, run ./configure, make, make install as the README instructs. Lots of warning but no errors. Yet I still can't configure mesa -- I get the same error as above. I tried installing libdrm to a different prefix and pointing mesa there. That didn't work either.
Any assistance would be appreciated. I am on Slackware64 14.1 multilib.
Also reuse the SlackBuilds for libdrm to rebuild a new package for libdrm then.
About using the libdrm and mesa packages for slackware-current; I didn't check, could be a hit or miss.
But what you could do is reuse the build material for -current to rebuild both packages, in case something did change in the SlackBuilds or maybe new patches applied: again, I didn't check.
All that been said, I'd suggest that you wait to fiddle with such important components of your system that you be more familiar with Slackware and its packaging system. http://docs.slackware.com can help you get there, especially all articles about Slackware packages that you can find using the search feature.
If you're attempting to do this on Slackware 14.1, you're in for a lot of recompiling. I did this last December to upgrade my mesa to 10.4, and it is a lot of work and a lot of dependencies. Keep in mind, this was for mesa back in December, so dependencies may have changed even further. The following is what I changed. The (recompiled) programs were needed so they worked with the other upgraded dependencies.
autoconf 2.69 (recompiled)
automake 1.11.5 -> 1.14.1
libdrm 2.4.46 -> 2.4.58
libelf 0.8.13 (recompiled)
libevdev 1.2 (added)
llvm 3.3 -> 3.4.2
mesa 9.1.7 -> 10.4
qt 4.8.5 -> 4.8.6
xorg 1.14.3 -> 1.15.2 (this was just the server version, but I didn't want to list each xorg package individually, since it was 276 packages)
Overall, it probably took me a week to get the everything upgraded properly. It contained some frustrating moments when I'd have a build fail due to outdated dependencies or when I'd attempt a reboot and something would crap out. Then I'd have to revert back to the stock packages and try again. Once everything was done, I then needed to do it all again in a 32bit VM so I could upgrade my multilib (but it's much easier to do it the second time than the first). It's definitely doable, but a better option might be to just switch to -current, since it has mesa 11.0.2 (and it'd likely be a really simple compile to upgrade to 11.0.3 if desired). But if you want to continue pursuing this, I would recommend starting with the source and slackbuilds from -current, and then only upgrade further when necessary. It's a lot easier than trying to just blindly update programs not using the work Pat has already done to get everything working together.
Thanks guys. I think Didier Spaier is correct that I should hold off until I have a better understanding of this. And I will most likely try out Slackware-Current rather than try doing it all myself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.