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

Nalin Dahyabhai nalin at redhat.com
Thu Sep 15 16:51:32 UTC 2005

On Thu, Sep 15, 2005 at 12:14:30PM -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?

We did include it in FC3, so any packages which depended on it and which
themselves included .la files would have hard-coded a reference to the

Between FC3 and FC4, the libxml2-devel package dropped the .la file, but
there's still a reference to it in the .la file which libgnomedb-devel
installs, suggesting that it didn't get rebuilt after libxml2 was
upgraded.  Rebuilding libgnomedb for FC4 should clear it up and let your
build proceed.



More information about the fedora-extras-list mailing list