[pkg-nvidia-devel] Bug#441975: Bug#441975: nvidia-glx should only provide the TLS version

Chris Reeves chris.reeves at iname.com
Thu Jul 24 16:32:07 UTC 2008

On Thu, Jul 24, 2008 at 08:48:07AM -0700, Randall Donald wrote:
> I was working on this yesterday based on your email. Just to confirm,
> will providing TLS-enabled libnvidia-tls in both /usr/lib
> and /usr/lib/tls work?

It depends upon what exactly your definition of "work" is. It works on my
lenny system (glibc 2.7, kernel 2.6.25) in as much as having the /usr/lib/tls
version of the library in both /usr/lib/tls and /usr/lib has had no adverse
effect on my running system (whether I boot with /etc/ld.so.nohwcap present or
not) and means that "perl -e 'use Qt'" does not segfault when
/etc/ld.so.nohwcap is present (which should prevent debconf from crashing when
the kde frontend is used).

As I said in my previous mail, IMHO there is no reason for both versions of
this library to be accessible by a running system at any one time (the
libraries are for use with different glibc and/or kernel versions). Therefore
/usr/lib and /usr/lib/tls should both contain the same version.

The question remains as to whether we wish to continue supporting nvidia-glx
users who use an unpatched kernel 2.4 (which your README.Debian implies are
the target users of the 'non-tls' version). If that is the case then we should
install both versions into /usr/lib/nvidia and continue to use USE_TLS to
switch between the versions. If not, then the one-line change that you made to
debian/rules in r432 should be sufficient to fix things on the nvidia-glx side
of things. Of course, libc6 would still need a Conflicts: or some other

I hope this is confirmation enough. My more reserved language is simply
because I have a limited ability to test this (the system that this applies to
is a production system).


More information about the Pkg-nvidia-devel mailing list