Re: Problem found -- autogen.sh won't find <name>-config in directories other than /usr/bin?

[James Henstridge <james daa com au>]

Do you have /usr/gnome/bin in your path?  This is important if you want to
install gnome into a location like this.  If you have another gnome
installation (maybe in /usr or /usr/local), make sure /usr/gnome/bin comes
before the other directories in the path.

Making this change should fix your problem.

James.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Mon, 11 Oct 1999, Miles Lane wrote:

> 
> I researched the problem I was having where esound wouldn't build
> when my audiofile libraries where installed in /usr/gnome/lib,
> even though I had specified "--prefix=/usr/gnome".  It seems that
> my audiofile-config file was not being found.  Due to this, the
> library location flag was still being set to "-l/usr/lib".
> 
> Another problem is that after encountering the error with not 
> finding audiofile-config, the compilation process continue,
> even though audiofile is now required for esound to build!
> 
> I am no Makefile/autogen guru, so hopefully someone else can check in
> fixes for this.  In the meantime, I have added:
> 
> 	cp /usr/gnome/bin/*-config /usr/bin
> 
> after each module compilation process in my build script. 
> It's a hack, but it appears to work.
> 
> Miles
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>