Re: Compilation problem with libexpat.

On Thu, 21 Apr 2005 00:13:47 -0400
Jody Goldberg <[email protected]> wrote:

> On Mon, Apr 18, 2005 at 02:25:59AM -0300, John Coppens wrote:
> > Hello people.
> > 
> > I have my libexpat in /usr/X11/lib, which is correctly included in all
> > paths, but for some reason, compiling libgnomeprint-2.8.2, insists
> > that it be in /usr/bin, and I have the following error:
> > 
> > ranlib .libs/libgnomeprint-lpr.a
> > creating libgnomeprint-lpr.la
> > /usr/bin/sed: can't read /usr/lib/libexpat.la: No such file or
> > directory libtool: link: `/usr/lib/libexpat.la' is not a valid
> > libtool archive make[3]: *** [libgnomeprint-lpr.la] Error 1
> > make[3]: Leaving directory `/usr/local/src/gnome2/libgnomeprint-2.8.2/
> > libgnomeprint/transports' make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/usr/local/src/gnome2/libgnomeprint-2.8.2/
> > libgnomeprint' make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/usr/local/src/gnome2/libgnomeprint-2.8.2'
> > make: *** [all] Error 2
> > 
> > configure doesn't complain, and I cannot find why libtool insists on
> > looking for it there.
> > 
> > Can anyone point me in the right direction?
> 
> You probably have a package that installed a .la file that
> references it there.  It shouldn't do that.

Thanks Jody.

That must have been the cause. I was updating loads of packages, tried
again later to compile gnome-print, and it worked without problems. I
wonder if there is a tool to crosscheck all libraries/.la's - that'd be
handy. According to reports on the 'net, lots of people have these kind of
problems.

Thanks!
John