From: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id: <200009271118.NAA05503@lws256.lu.erisoft.se>
Subject: Re: Building binutils 2.95.1
To: tim DOT vanholder AT falconsoft DOT be (Tim Van Holder)
Date: Wed, 27 Sep 2000 13:18:06 +0200 (MET DST)
Cc: djgpp AT delorie DOT com
In-Reply-To: <200009271057.MAA05457@bashir.belgium.eu.net> from "Tim Van Holder" at Sep 27, 2000 12:57:01 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

> Obviously drunk, "Martin Stromberg" <eplmst AT lu DOT erisoft DOT se> wrote about

Uhh!?

> The -1 suggests that command.com is being used as shell and asked
> to invoke something it doesn't know about.
> The fact that it's the config.h rule suggests something like this:
> 
> config.h: blah blah
> 	@true

The exact line is "config.h: stamp-h ; @true"

> command.com doesn't have a 'true' command, so it barfs.
> 
> The solution will likely be to put either
> SHELL = /bin/sh
> in the offending Makefile, or (preferably) in Makefile.in (so it stays
> set if you reconfigure).
> For recent autoconfs (2.13 is new enough, I think), you can
> put
> SHELL = @SHELL@
> in Makefile.in instead.

But there already is a line that says "SHELL = sh" in the
makefiles. And "type -p sh" in bash points out sh.exe in djgpp/bin.


Right,

						MartinS