Message-ID:	<35169791.BC0A76AC@gmx.net>
Date:	Mon, 23 Mar 1998 18:10:41 +0100
From:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization:	none provided
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>, djgpp AT delorie DOT com,
	pavenis AT laima DOT acad DOT latnet DOT lv
Subject:	Re: Building gcc-2.8.1 for DJGPP
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980323131551 DOT 1968I-100000 AT is>

Eli Zaretskii wrote :
> 
> Try this:
> 
>     O:\TMP>cat test
>     #!/bin/sh
>     test1

This works, but this is not the real problem of the original
poster. The real problem is the line with

/bin/sh ...

where one script calls an other with an explicit shell.
After looking now again in the configure script I found,
that the problem is in the following lines

${CONFIG_SHELL-/bin/sh} ....

which means, when the variable $CONFIG_SHELL is not set, the
script tries to run /bin/sh. To solve this, simply set this
variable before running the configure script either global
via SET or in the djgpp.env or in the djconfig.sh with a

export CONFIG_SHELL=bash

Robert
-- 
******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************

- Raw text -