Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 get that error when loading some shared libraries (specifically, libGL.so from ATI drivers and libjemalloc.so from Firefox 3).
What does that mean? Is TLS the same as "Transport layer security"? Libraries use TLS? To talk to whom? And above all, how do I fix this problem?
Thank you!
Yes, it's *that* TLS, the one that has to do with NPTL. IIGC the problem occurs when libraries get provided (external, binary drivers) and loaded that should *not* be TLS-enabled. Cursory search shows quite a few possibilities to test ranging from LD_PRELOADs to LD_ASSUME_KERNEL to reverting to earlier builds (like in your other thread) to rebuilding w/o TLS...
I didn't understand one thing: my C library are TLS-enabled and the shared libraries aren't, or is it the other way round?
Anyway, should upgrading glibc work? If yes, how can I upgrade glibc without messing up all the libraries compiled against it?
Thank you!
IIRC in your other thread you downgraded the drivers to a previous version (and I think non-TLS). IIGC, and as far as I've read, it'll be a situation where the supplied driver forces TLS where it shouldn't, and that as such it isn't about upgrading Glibc. Of course I could be totally off my rocker here.
IIRC in your other thread you downgraded the drivers to a previous version (and I think non-TLS). IIGC, and as far as I've read, it'll be a situation where the supplied driver forces TLS where it shouldn't, and that as such it isn't about upgrading Glibc. Of course I could be totally off my rocker here.
What do you think I should do in order to get TLS - and those libraries - working?
Thank you!
I think the problem is more serious than I thought... Many recent binaries use TLS - so I can't use them!
Forgive me if I repeat my request: doesn't anyone know how to enable TLS in Linux??
Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
