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.
Is there any reason to not update to eudev-3.2.7? It resolves a trivial, but annoying issue here where when I use my Sony Playstation3 Controller with a program that uses libinput (i.e. wine) it prints this for every button press filling the logs with garbage.
Code:
(EE) libinput bug: Event for missing capability CAP_POINTER on device "Sony PLAYSTATION(R)3 Controller"
For more info please see this libinput issue where it was debugged.
I'd like to have binutils (libbfd, in particular) built with --enable-targets=all instead of how it's currently set up. This will make objdump and other tools more capable of picking apart various other executables and libraries.
Anyone know what causes this, from ./configure (autoconf), compiling libaacs in -current:
Code:
configure: WARNING:
***
*** The config script /usr/bin/libgcrypt-config was
*** built for x86_64-slackware-linux-gnu and thus may not match the
*** used host x86_64-pc-linux-gnu.
*** You may want to use the configure option --with-libgcrypt-prefix
*** to specify a matching config script.
***
Anyone know what causes this, from ./configure (autoconf), compiling libaacs in -current:
Code:
configure: WARNING:
***
*** The config script /usr/bin/libgcrypt-config was
*** built for x86_64-slackware-linux-gnu and thus may not match the
*** used host x86_64-pc-linux-gnu.
*** You may want to use the configure option --with-libgcrypt-prefix
*** to specify a matching config script.
***
maybe this is not the proper topic, you better open a new one...
BTW, I don't know which SlackBuild you are using but libaacs from SBo seems to build fine for me on slackware64-current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.