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.
My point was to beware of creeping feature-isms. That is all.
Ed
The xdg-desktop-portal has a precise purpose, which people (including me) appreciates well. That's why it was also added on Slackware, for Wayland support.
If your purpose is not to request to remove it (to which I disagree) then your posts on this thread are, well... not that on topic.
Last edited by LuckyCyborg; 12-28-2021 at 12:59 PM.
tl;dr there's no harm enabling OpenCL support in ImageMagick for the ones not having OpenCL capable hardware or its drivers not installed. It can also be disabled at runtime (for the ones having OpenCL capable hardware and drivers in place) by using `MAGICK_OCL_DEVICE=OFF convert`.
tl;dr there's no harm enabling OpenCL support in ImageMagick for the ones not having OpenCL capable hardware or its drivers not installed. It can also be disabled at runtime (for the ones having OpenCL capable hardware and drivers in place) by using `MAGICK_OCL_DEVICE=OFF convert`.
It used to be enabled but was leading to hangs. Some drivers are of better quality than others.
I could possibly see enabling it in the future with a default of MAGICK_OCL_DEVICE=OFF set in a /etc/profile.d/ script, but not now.
It used to be enabled but was leading to hangs. Some drivers are of better quality than others.
I could possibly see enabling it in the future with a default of MAGICK_OCL_DEVICE=OFF set in a /etc/profile.d/ script, but not now.
Thanks for taking the time to reply, @volkerdi.
That's a perfectly valid reasoning and a totally acceptable approach to handle it in the future. I'll just grab the source and compile it myself meanwhile.
If you can live with this only working for the installer option 5 "Install from FTP/HTTP server" running in 'full' or 'terse' mode (i.e. no tagfiles), and inaccurate package sizes being displayed for newer packages, then you could try this technique.
- Copy the two attached patch files to a device that can be mounted from the installer before running 'setup'.
- Boot the installer and create a directory with 'mkdir /mnt/hd'.
- Mount the device with 'mount <device> /mnt/hd'.
- Patch INSURL with 'patch /usr/lib/setup/INSURL /mnt/hd/<path>/<to>/INSURL.patch'.
- Patch slackinstall with 'patch /usr/lib/setup/slackinstall /mnt/hd/<path>/<to>/slackinstall.patch'.
- Unmount the device with 'umount /mnt/hd'.
- To be clean, remove the directory with 'rmdir /mnt/hd'.
- Run 'setup' as normal.
.
.
.
Hey allend! That seems like a big thing. I appreciate your effort. I run multiple virtual machines with 14.2, so next time I create one, I will use this method.
Thanks a lot!!
It used to be enabled but was leading to hangs. Some drivers are of better quality than others.
I could possibly see enabling it in the future with a default of MAGICK_OCL_DEVICE=OFF set in a /etc/profile.d/ script, but not now.
@volkerdi, I've downloaded imagemagick source SlackBuild and changed the following:
Code:
--- imagemagick.SlackBuild 2021-05-31 16:19:59.532025603 -0300
+++ imagemagick-opencl.SlackBuild 2021-12-30 05:56:45.456301573 -0300
@@ -23,7 +23,7 @@
cd $(dirname $0) ; CWD=$(pwd)
PKGNAM=imagemagick
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2deny}
# NOTE: This is to cope with ImageMagick version numbers such as 5.4.7-4,
# which occur fairly often (but not always). If these numbers are all the same,
@@ -114,7 +114,7 @@
--with-x \
--with-frozenpaths=no \
--with-modules \
- --disable-opencl \
+ --enable-opencl \
--enable-hdri \
--enable-static=no \
--enable-shared \
I've searched in Slackware's source but it only shows imagemagick.SlackBuild with already --disable-opencl.
Do you have a clue on when you've made that change or its diff?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
