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 just wanted to warn the Slack team that since the commit of the new GLSL compiler from Intel to mesa, there was a hard dependency introduced on the talloc library, which is right now provided in Slackware within the Samba package.
However, I could only compile a recent mesa git pull by creating a "/usr/lib64/pkgconfig/talloc.pc" file, following the advice of nanonyme, on Phoronix.
The file has been copied from Fedora :
Code:
Code:
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib64
includedir=/usr/include
Name: talloc
Description: A hierarchical pool based memory system with destructors
Version: 2.0.1
Libs: -L${libdir} -ltalloc
Cflags: -I${includedir}
URL: http://talloc.samba.org/
After that compilation could work.
Since there's a fair chance that this is to stay, I thought that maybe the Slack team, and some others, could be interested in this trick.
Best regards,
Click here to see the post LQ members have rated as the most helpful post in this thread.
Irecently tried to do the same. But didn't figure out that this lib is already included with slackware. So i downloaded talloc 2.0.1, and installed it as a separate package.
PS didn't have time yet to check. But isn't simple symlinking libtalloc.so-2.0.1 to libtalloc.so-2.0 should resolve this problem?
You are absolutely right. I wrote above message from my memory, which was wrong. After installing talloc from a separate package from http://talloc.samba.org/ (I used modified slackbuild from slackware samba script), I actually have this:
Almost surely some CFLAGS-fu and LDFLAGS-fu (and there might even be TALLOC_CFLAGS and TALLOC_LDFLAGS (or similar) variables that one can use to override pkg-config) would fix this without having a libtalloc.pc file, but this is handy to know nonetheless. Assuming samba will use an external libtalloc if it's present, and the ABI is stable, and so on, then probably the best option will be to split libtalloc out of the samba package when the time comes. We'll see. :-) Thanks for the heads-up.
I think, that best way is just add "-ltalloc" to LDFLAGS (-L flag is already set with --libdir switch of configure script). This is most secure way IMHO, if You don't want to add libtalloc.pc file I don't know, if changing CFLAGS has something to do with this problem
Please, let us know, it this solved the problem - I don't want to utilize my CPU for useles for me compilation processes
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.