[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in generation of static link lines for three specific libraries
From: |
Eric S. Raymond |
Subject: |
Re: Bug in generation of static link lines for three specific libraries |
Date: |
Thu, 17 May 2007 23:56:54 -0400 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
Noah Misch <address@hidden>:
> This `.la' file tells Libtool that there is no static library, even
> though there is one. Either the Libtool that generated this library
> was buggy, or something edited the file after Libtool wrote it.
Identical misbehavior was reported in 2004 on a Red Hat system. I
think it's unlikely that something clobbered these files in exactly the
same way twice.
> Try editing this to be `old_library='libglib-2.0.a''. Then do
> likewise for the `.la' files of the other problematic libraries.
That worked. At least, I now get a different error, perhaps also
symptomatic of a problem in the way libtool generates command lines
for static linking...
/usr/lib/libSDL.a(SDL_sysloadso.o): In function `SDL_LoadObject':
(.text+0xf7): warning: Using 'dlopen' in statically linked applications
requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: cannot find -lpython2.5
collect2: ld returned 1 exit status
> What type of system is this? If GNU/Linux, what distribution and version?
It's a pretty stock Ubuntu Feisty Fawn 7.04 for AMD64.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>