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.
I have tried the same ting as PJBrs talked about. I got the Frankenware to work in the end with a LOT of work.
All I got for the trouble was a unupgradeable system that required even more work. Just don't do it is My advice.
I did this on two different multilib systems, and while I said it was a chore, they certainly remain upgrade-able with slackpkg. Just blacklist some stuff. Since I did this a long time ago, I don't know the exact details anymore, but my local ~/Packages/mesa directory has the following list of packages:
[NOTE, it was llvm-6.0.1 not llvm-8.0 as I wrote earlier]
I guess I may have already had python3 64-bit installed before I upgraded mesa, but I think these are the necessary packages for updating mesa. So, I don't think it is as difficult as you make it seem right now. Then again, as I said, your mileage may vary...
What you mean is that you compile the packages you listed above, from source, every time there's a security upgrade
and that you do that in a system where the ability to do so changes over time.
Would you recommend that to a new user ?
What you mean is that you compile the packages you listed above, from source, every time there's a security upgrade
and that you do that in a system where the ability to do so changes over time.
Would you recommend that to a new user ?
Well, I'll admit that I haven't recompiled these packages in a long time. Didn't notice any security issues in them either, but perhaps I'm not paying enough attention.
What would I recommend?
Well... I just answered the original question right? I'll leave the decision to the OP.
My personal consideration - I assume that any Slacker will either be able to quickly compile some packages, or will want to learn how to do so. Then my suggestion would seem reasonable. However, I personally am starting to grow more and more hesitant recommending new users either option - I think new users should not install non-stable editions (even though -current appears quite stable in practice), nor would I recommend users to compile stuff from source by necessity, just because they want to use 14.2 with newish hardware (new AMD CPUs and GPUs).
I think that the need for a new stable release is growing. But let's not get off on that tangent ;-)
Well, I'll admit that I haven't recompiled these packages in a long time. Didn't notice any security issues in them either, but perhaps I'm not paying enough attention.
What would I recommend?
Well... I just answered the original question right? I'll leave the decision to the OP.
My personal consideration - I assume that any Slacker will either be able to quickly compile some packages, or will want to learn how to do so. Then my suggestion would seem reasonable. However, I personally am starting to grow more and more hesitant recommending new users either option - I think new users should not install non-stable editions (even though -current appears quite stable in practice), nor would I recommend users to compile stuff from source by necessity, just because they want to use 14.2 with newish hardware (new AMD CPUs and GPUs).
I think that the need for a new stable release is growing. But let's not get off on that tangent ;-)
new user like me run away from hell of other distros wich broke at random time specialy after an update; starting using Slack no broke system , and I boot my Pc with confident every time that it work and it did sometimes I think Slack will boot even without power cable plugged IoI , last time I compliled stuff back when I want to use skype ...alsa dropped and pulse take place , and it work without borken , so I understand both yr points of view toward new slack's user ,thank you very much and be safe. be Slack's helpers IoI.
Hello
After installing the live edition of slackware using the setup2hd , all work fine , video sound via Hdmi ..but i noticed it took a while before the Kde desktop load , finaly I decide to try the current edition ; so the gate of questions and help is opened again
so be ready plz thank you
Note - tested on only one machine. These packages will give you mesa-19.2.2 on Slackware 14.2.
@rogan - I'll admit this took a lot longer than I had expected...
*EDIT*
Just tested them on my intel laptop. I noticed that glxgears was missing from the 64-bit package. Other than that, I just got steam in-home streaming to work from slackware to slackware :-)
Just tested them on my intel laptop. I noticed that glxgears was missing from the 64-bit package. Other than that, I just got steam in-home streaming to work from slackware to slackware :-)
No, they complain about missing libGL.la - since mesa switched to the meson build system it doesn't ship *.la files anymore. But I found a patch from Linux from scratch that adds back only glxinfo and glxgears, and they build fine.
Somehow, though, the /usr/bin/32/glx{gears,info} packages are present in the compat32 package, showing that they do build fine.
No, they complain about missing libGL.la - since mesa switched to the meson build system it doesn't ship *.la files anymore. But I found a patch from Linux from scratch that adds back only glxinfo and glxgears, and they build fine.
Do you have a link for that patch? I remember running into that problem a few months ago.
No, they complain about missing libGL.la - since mesa switched to the meson build system it doesn't ship *.la files anymore. But I found a patch from Linux from scratch that adds back only glxinfo and glxgears, and they build fine.
Somehow, though, the /usr/bin/32/glx{gears,info} packages are present in the compat32 package, showing that they do build fine.
You might want to read the changelog entry from a while ago when all of the .la files were removed.
I also rebuilt my 64-bit mesa package, which now does include glxinfo and glxgears.
Quote:
Originally Posted by orbea
You might want to read the changelog entry from a while ago when all of the .la files were removed.
Yes I read that. But I'm building on 14.2, which still has all these .la files. Even building libdrm without them is hard. The mesa-demos want to link to libGL, and apparently they expect mesa to ship with libGL.la for that purpose. But since version 19, mesa switched from an autotools build system, which generates .la files, to the meson build system , which doesn't produce these .la files. So, on a 14.2 system (probably because libGL.la is needlessly referenced somewhere on 14.2, and I couldn't be bothered to find out where exactly), the mesa-demos fail to build against mesa-19 and further on.
Funnily, if you build mesa 19.2.2 with an old mesa installed, the mesa-demos build will succeed because it will link against the old mesa libs.
For now, I've kept all the .la files in libdrm. I'll get rid of them when I switch to 15.0
Hello
After installing the live edition of slackware using the setup2hd , all work fine , video sound via Hdmi ..but i noticed it took a while before the Kde desktop load
The bottleneck in your case is the 1Tb WD drive if that's what you're using. Get a SSD! You could
probably buy a new 120Gb-ish dirt cheap. It's plenty of room for your system if you use the old WD on your /home
The KDE desktop is a resource hogger and you should expect it to take a while to load because it's _big_ .
Once it's loaded, it should be pretty snappy though, at least if you disable the baloo desktop indexer file
content search ability.
The functionality and user experience in the new (plasma-5) desktop is second to none in my experience and you
_really_ should switch to it if KDE/fully featured desktops is your thing: http://slackware.uk/people/alien-kde/current/latest/
It will probably be included pretty soon anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.