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.
The first diff was to remove the previously existing --enable-opencl, but the compile still enabled the option automatically. The second diff was to add --disable-opencl as currently exists in the SlackBuild.
Probably not helpful, sorry. Not sure what else you'd need to do if disable -> enable isn't enough to make it work.
Yeah, I've seen that just by removing --enable-opencl wasn't enough to disable it, thus --disable-opencl was explicitly required. Probably --enable-opencl alone is not enough to make it work either although binaries clearly states otherwise.
I'll keep researching on that and ping here if succeed. Thanks, @volkerdi.
@volkerdi, maybe you're interested to know that IM has received some patches to avoid "the others", starting from 7.0.11-7.
Let me handle this new issue upstream then you may be good to go on getting OpenCL enabled back again on imagemagick whenever you feel the time is right.
Why not ? For example libadwaita has been released right these days and minimum gtk requirement is gtk 4.5.x. But many other
gnome components will be ported on, so since right now nothing is really dependant on gtk4 in slackware I think there is
no big risk to g with the latest stable one.
Why not ? For example libadwaita has been released right these days and minimum gtk requirement is gtk 4.5.x. But many other
gnome components will be ported on, so since right now nothing is really dependant on gtk4 in slackware I think there is
no big risk to g with the latest stable one.
I'm just making a deduction
We didn't move to 4.5.0 in october
So I concluded that we would stay on the 4.4.x branch
I understand that, but the branch of gtk 4.5.x was the one who took us to now to a stable gtk 4.6.x . I am just asking to go with the latest one since, when slackware stable is released, most probably will be much difficult to get a newer release in it.
Therefore, having a latest base now in it will remove the need to upgrade later, although if nothing depends on it, wont change much.
But as far as I can see the things in the gnome world are more and more ported to gtk 4.
I understand that, but the branch of gtk 4.5.x was the one who took us to now to a stable gtk 4.6.x . I am just asking to go with the latest one since, when slackware stable is released, most probably will be much difficult to get a newer release in it.
Therefore, having a latest base now in it will remove the need to upgrade later, although if nothing depends on it, wont change much.
But as far as I can see the things in the gnome world are more and more ported to gtk 4.
some things on -current are using gtk4 libs , but probably can be rebuild if libs change numbers and break something, cause only 2 or 3 packets depends on it on -current.
some things on -current are using gtk4 libs , but probably can be rebuild if libs change numbers and break something, cause only 2 or 3 packets depends on it on -current.
I do not see any thing that uses GTK4, in current, but I can be wrong
Curious on archlinux 'libinput' is compiled with gtk+3 but no with gtk4
Probably cause autodetect want the more up version , but arch require gtk3 , not sure if exist a flag config to choose , probably if you remove gtk4 and rebuild libinput he links against gtk3 cause no gtk4 available.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
