cannot handle TLS data

[Ken Causey]

I hope this is an appropriate place to ask this.  If not I would really
appreciate it if you could point me towards a more appropriate forum.

I'm having an issue with thread local storage and NVidia OpenGL
libraries.  I'm coming at this from an application developer's
standpoint to understand how I should properly handle this.  I'm using
an open source game development library (nebula device) that has a
shared library that is linked to the GL libraries.  The shared library
is dynamically loaded.  When it is loaded I get a dlerror() of

libGL.so.1: cannot handle TLS data

In the NVidia drivers README I found a workaround that involves setting
the LD_ASSUME_KERNEL environment variable to something less than 2.3.99
which forces the use of the non-TLS opengl libs at which point
everything works.

I'm running a reasonably up to date (maybe a week behind) Debian
unstable installation and though this issue has come up in the past as a
problem with a Debian package I believe this has long been fixed and so
doubt that the problem is with the Debian installation.

I have installed the 5396 version of the Nvidia drivers and I installed
them using the .run script so they should be properly installed.

What I'm trying to figure out is whether this could be a problem with
the nebula device shared library or with the way it is built and if it
is something I can fix by changing the source or the build setup in some
way.

Thank you for your assistance,

Ken Causey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20040427/a7572a23/attachment.sig>