Date: Wed, 1 Apr 1998 11:24:15 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Hogan <billh AT ferrari DOT autobahn DOT org>
cc: djgpp AT delorie DOT com
Subject: Re: ./configure
In-Reply-To: <slrn6i1ral.teq.billh@ferrari.autobahn.org>
Message-ID: <Pine.SUN.3.91.980401112357.2919J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 31 Mar 1998, Bill Hogan wrote:

> ----------------------- quote --------------------
> loading cache ./config.cache
> checking for sh... no
> checking for bash... no
> checking for zsh... no
> checking for ksh... no
> oops - no usable shell for make or me! Configure is exiting.
> ---------------- unquote -------------------------
> 
>  My question: given that I have a standard djgpp-v2 setup,
> what is it that prevents this script from finding the things
> it is looking for?

It is looking for the shell.  I cannot really guess why is it failing,
since none of the configure scripts I've seen does that, so please
post the part of the script which does these tests if the advice below
doesn't help.

First, look at the file `config.log'.  The material there could well
explain what does the script do and why does it fail.

I assume that you have the DJGPP port of Bash installed.  If so,
please make sure you have a ``symlink'' to bash.exe called sh.exe in
the same directory.  If you don't, go to the directory where you keep
bash.exe and type the following:

	 ln -s bash sh

(`ln' is a program from the GNU Fileutils package).

The next step is to set the following two variables in the environment
before running the script:

         set PATH_SEPARATOR=:
	 set PATH_EXPAND=y

If that doesn't help, make sure you have all the programs the script
could call installed.  In general, all of the packages below need to
be installed in order to be sure Unix shell scripts will run:

	 Fileutils
	 Textutils
	 Grep
	 Sed
	 Sh-utils
	 Gawk
	 Diffutils

All of these are available from the DJGPP sites, in the v2gnu directory.

Finally, if it still doesn't work, look at the tests the script
performs to find the shell.  If it looks for the shell executable file
with something like "test -f $shell", change `-f' to `-x' and try
again.  (On MS platforms, there is no `sh' or `bash', there's `sh.exe'
and `bash.exe'; "test -x" knows about that, but "test -f" does not.)