Date:	Wed, 8 Jan 1997 09:46:20 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Michael Gierhake <GEIER AT LaDune DOT Prometheus DOT De>
cc:	djgpp AT delorie DOT com
Subject:	Re: Configure scans wrong directories?
In-Reply-To:	<6OP1rB8pgzB@bahaya.ladune.prometheus.de>
Message-ID:	<Pine.SUN.3.91.970108094211.28968S-100000@is>
MIME-Version:	1.0

On Mon, 7 Jan 1997, Michael Gierhake wrote:

> E.g., if I say:
> 
>         configure --target=i386-go32 -libdir=/usr/i386-go32/lib \
>         --includedir=/usr/i386-go32
> 
> the results are still based on what configure finds in the default
> LinuX 'lib' and 'include' directories. As a result, the Makefiles
> and config.h's produced by configure tend to be well-nigh useless.
> 
> Is there anything I can do about it?

configure scripts only look in certain directories, and your 
cross-compiling directories are probably not in the list of the places 
known to the scripts.  However, the script has an option for you to tell 
exactly where the include files and libraries are, like so:

	configure --includedir=DIR --libdir=DIR ...

- Raw text -