Date: Sun, 26 Oct 1997 16:52:41 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Hans Ecke <ecke AT coffee DOT geophysik DOT tu-freiberg DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: Running programs from inside bash
In-Reply-To: <Pine.HPP.3.96.971024170601.10598A-100000@coffee.geophysik.tu-freiberg.de>
Message-ID: <Pine.SUN.3.91.971026165209.17911K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 24 Oct 1997, Hans Ecke wrote:

> I also noticed, that I can call any program from inside bash like this :
> c:>c:/command.com /c nc.exe
> But it should be a blame, that bash is not able to load&execute simple dos
> executables!

I suspect that the following variables are the culprit:

> PATH_EXPAND=Y
> PATH_SEPARATOR=;
> PATH_SLASH=\
> SYSROOT=

If you don't set SYSROOT and your PATH_SEPARATOR=;, then you don't
need to set PATH_EXPAND=Y.  These four variables are for Unix shell
scripts, you don't need them at all if all you run is DOS and DJGPP
programs.  So the first thing I would suggest to try is to unset these
all, and see if that helps.  If it does, then don't set them until you
see some shell script that breaks.

Here's what I think is going on: PATH_EXPAND=Y causes Bash to convert
strings with forward slashes into DOS-style backslashified path
names.  If this happens with strings which aren't file names, you
lose.