Re: [E-devel] Problem when testing for XShmAttach()

[Gordon Heydon <gjheydon@bigfoot.com>]

Thanks for your help, but I didn't really get me too far, I checked it
and it looked a bit wierd (well to me) 

        libX11.so.6 => /usr/lib/libc5-compat/libX11.so.6 (0x4001b000)
        libc.so.6 => /lib/libc.so.6 (0x400b7000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)

The dependancy on the libc5-compat version of libX11 looks funny to me,
and I did have libc5 on my system and I not so long ago I had removed it
as I wasn't using it. I did try to reinstall it, but still the same
problem.

I am not really sure still where to go from here, but I will keep on
working.

Thanks

Gordon.

* Matt Schalit (mschalit@pacbell.net) wrote:
> Gordon Heydon wrote:
> > 
> > Hello,
> > 
> > I am posting this to both the e-development and the debian-x as I am not
> > exactly not which list to send it too.
> > 
> > When I am triing to build imlib2 it fails during the configure I get the
> > error below from the config.log :-
> > 
> > configure:2964: checking for XShmAttach in -lXext
> > configure:2983: gcc -o conftest -g -O2   conftest.c -lXext  -L/usr/X11R6/lib   1
> > >&5
> > /usr/X11R6/lib/libXext.so: undefined reference to `_Xglobal_lock'
> > /usr/X11R6/lib/libXext.so: undefined reference to `_XUnlockMutex_fn'
> > /usr/X11R6/lib/libXext.so: undefined reference to `_XLockMutex_fn'
> > collect2: ld returned 1 exit status
> > configure: failed program was:
> > #line 2972 "configure"
> > #include "confdefs.h"
> > /* Override any gcc2 internal prototype to avoid an error.  */
> > /* We use char because int might match the return type of a gcc2
> >     builtin and then its argument prototype would still apply.  */
> > char XShmAttach();
> > 
> > int main() {
> > XShmAttach()
> > ; return 0; }
> > 
> > So either there is unmet dependancies in Xext or imlib2 is not including
> > something that it should be. maybe I am right, maybe I am wrong, but can
> > someone help me.
> > 
> > Now I am not too sure where to go from here, Could some please help me.
> > 
> > Gordon.
> 
> 
> You probably got the answer by now, but if not, the answer is that
> you can do an ldd /usr/X11R6/lib/libXext.so and see what all the
> dependancies are.
> 
> Usually what I also do is just do a man on the function it can't find, 
> like man mutex_lock.  It was likely that you Xext was compiled to use 
> threads, so you need to add a LIBS=-lthread or -lpthread or whatever 
> you find with man or ldd.
> 
> Take it easy,
> Matt