FC4 Build error due to libtool la dependency hell on ppc only, fine on i386

Michael Schwendt bugs.michael at gmx.net
Thu Sep 15 16:55:15 UTC 2005


On Thu, 15 Sep 2005 12:14:30 -0400, Dan Williams wrote:

> On Thu, 2005-09-15 at 18:09 +0200, Hans de Goede wrote:
> > grep: /usr/lib/libxml2.la: No such file or directory
> > /bin/sed: can't read /usr/lib/libxml2.la: No such file or directory
> > libtool: link: `/usr/lib/libxml2.la' is not a valid libtool archive
> > make[3]: *** [gdaif.la] Error 1
> > make[3]: Leaving directory 
> > `/builddir/build/BUILD/gnumeric-1.4.3/plugins/gda'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/builddir/build/BUILD/gnumeric-1.4.3/plugins'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/builddir/build/BUILD/gnumeric-1.4.3'
> > make: *** [all] Error 2
> > 
> > ---
> > 
> > I know this is caused by libtool dependency hell, the strange thing is I 
> > did a mock build on i386 and that went fine.
> 
> AFAICT, we don't _ship_ a libxml2.la anywhere, not in the libxml2-devel
> package, nor in the libxml2 package.  Another libtool suckage issue?

Libtool doesn't suck. Often such an error indicates an old -- and now
broken -- libtool inter-library dependency which is hardcoded in a libtool
archive used here and which requires rebuilding one of the build
dependencies of this package. Does libgda on FC4 possibly contain a
broken libtool archive which refers to libxml2.la?




More information about the fedora-extras-list mailing list