[pkg-nvidia-devel] nvidia-glx shlibs issues

Russ Allbery rra at debian.org
Sun Jun 27 23:55:18 UTC 2010


Andreas Beckmann <debian at abeckmann.de> writes:

> Having looked into this "mess" again, the situation is as follows: no
> matter where libGL.so pointed to while linking some program binary, at
> the time the dependencies are generated by dpkg-shlibdeps only
> libGL.so.1 is interesting. Therefore we need a shlibs file "redirecting"
> the dependency to 'libgl1-mesa-glx | libgl1' and *no symbols file*
> because this overrides a shlibs file. Fixed in SVN (hopefully).

Well, we could also change the symbols file to similarly redirect things
to the appropriate set of packages.  I think it supports the same
functionality.  But yes.  Sorry, I hadn't thought through that.

> But if libGL.so is not that interesting any more, what about dropping
> its diversion and the trigger and the related mess?  If you want to
> build OpenGL programs install libgl1-mesa-dev. libGL.so will point to
> libGL.so.1 (which is from nvidia, but this should not matter).

This is the problem: I think this does matter.  If the MESA libGL ever
includes any symbols that aren't in the NVIDIA library, which doesn't seem
that horribly unlikely, linking would then fail because libGL.so would
point to the wrong library.  Since we have a solution to keeping the *.so
file up-to-date, I think we should leave it just in case.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>



More information about the Pkg-nvidia-devel mailing list