Thomas Tanner wrote:
> 
> On 13-Feb-00 Brian Paul wrote:
> >> Is there any reason Mesa 3.3 is building without link information
> >> in the library? Those of us who dlopen() the library get a dl_error
> >> because we can't anticipate the need of, say, Glide.
> > I guess you're using the GNU configure scripts, right?
> ...
> > Using the GNU Makefiles:
> > % ldd libGL.so.1
> >         libc.so.6 => /lib/libc.so.6 (0x4024d000)
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> >
> > This is a problem in the configure or libtool scripts.  Hopefully
> > Thomas Tanner (or someone knowledgable in GNU configure) can look
> > into this.
> 
>  That's a bug in the libtool CVS snapshot Mesa 3.3 is using.
>  I'll try to fix it ASAP.


Thanks.  I'd like to elaborate on this.  The Linux/OpenGL standard
calls for libGL.so to be built with implicit links to all other
libraries which it depends on.  I've been working on fixing this
in the old-style makefiles.  I'll be checking that in soon.

Here's what the old-style makefiles are going to do:

libGL.so implicitly links with:
        libX11
        libXext
        libm
        libpthread
        libglide2x / libglide3x  if build with 3dfx support
        libvga  if build with SVGA driver

libGLU.so implicitly links with:
        libGL
        libm

libglut.so implicitly links with:
        libGLU
        libGL
        libX11
        libXmu
        libXt
        libXi
        libm

I've removed the -lICE and -lSM libs since I don't see the need
for them.

Can we implement the same thing with libtool?

-Brian


_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to