Date:	Wed, 26 Apr 2000 07:00:46 +0500
Message-Id:	<200004260200.HAA00879@midpec.com>
From:	Prashant TR <prashant_tr AT yahoo DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<3905B9E3.C6DA3661@worldaccessnet.com> (rhunt@worldaccessnet.com)
Subject:	Re: Question about running configure script
References:	<3905B9E3 DOT C6DA3661 AT worldaccessnet DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> They also tell you that 'configure' (actually 'configur' in my DOS
> environment) is affected by several environment variables, like 'CC' which
> controls which c compiler to use, and 'CFLAGS' which specifies the C
> compiler flags to use.  The README states that if you are using sh, bash,
> ksh, ash, or some other Bourne-like shell, you can simply set the variables
> on the command line, for example:
>     $ CC="gcc" CFLAGS="-g -O3" ./configure
> and that if you are using csh, tcsh, or some other C-shell, you set the
> variables by using setenv, for example:
>     $ setenv CC "gcc"
>     $ setenv CFLAGS "-g -O3"
>     $ ./configure

Another way is to edit the configure scripts and replace all
"test -f $ac_dir/$ac_word" with "test -x $ac_dir/$ac_word". Use something like
"s/test -f \$ac_dir\/\$ac_word/test -x $ac_dir\/$ac_word/g" in the sed script.

> Am I on the right track in assuming that I need to use something like BASH
> for this configure process?

Yes, you need BASH (available from v2gnu on Simtel).

- Raw text -