Date: Mon, 10 May 1999 09:39:56 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michael Bukin <M DOT A DOT Bukin AT inp DOT nsk DOT su>
cc: djgpp AT delorie DOT com
Subject: Re: Trouble Running Configure for Bash-2.03
In-Reply-To: <20yaixycr7.fsf@Sky.inp.nsk.su>
Message-ID: <Pine.SUN.3.91.990510093931.2882N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 10 May 1999, Michael Bukin wrote:

> Create /bin/sh.exe on current disk by copying bash.exe.

No need to copy; you can use the simulated ``symlink'' feature:

	cd c:\djgpp\bin
	stubify -g sh.exe
	stubedit sh.exe runfile=bash

This creates a 2KB-long sh.exe which, when invoked, will run the code
from bash.exe (provided they both reside in the same directory!) but
will pass "sh.exe" in argv[0].

> Go to the directory with configure.in and run autoconf
> (v2gnu/acnfNNb.zip) from bash.

Building DJGPP ports should not require running Autoconf at all.