Re: [Fwd: Could not autogen.sh]
- From: Gleef <gleef capital net>
- To: "David J. Orme" <david coconut-palm-software com>
- cc: Gnome List <gnome-list gnome org>
- Subject: Re: [Fwd: Could not autogen.sh]
- Date: Thu, 12 Nov 1998 22:59:24 -0500 (EST)
On Thu, 12 Nov 1998, David J. Orme wrote:
> Jeff Garzik wrote:
> > David J. Orme wrote:
> > > Is this bad behavior from aclocal (ie old version) or is it bad
> > > behavior from the glib install script (ie buggy glib install)?
> >
> > Bad behavior from me, aclocal knows its prefix. :)
> >
> > If you are taking the "anything non-RPM in /usr/local" attitude you
> > are going to have a rough life continuing to mix programs built for
> > /usr and /usr/local. Maybe consider un-installing autoconf, automake,
> > libtool RPMs, and installing them manually into /usr/local. Once that
> > is done, and /etc/ld.so.conf knows about /usr/local/lib, then life
> > should be grand.
>
> Sounds like a good idea. Does anyone know what RPM to uninstall in
> order to get rid of autoconf/automake?
On my machine, autoconf, automake and libtool are in the RPMs named
"autoconf", "automake" and "libtool", respectively.
In general, you can find out which RPM contains a binary by typing:
$ rpm -qf `which <binary>`
For example, to find the autoconf RPM, type:
$ rpm -qf `which autoconf`
Best of luck,
-Gleef
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]