Date: Tue, 25 Jan 2000 09:46:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Frank Donahoe <fdonahoe AT wilkes1 DOT wilkes DOT edu>
cc: DJGPP List <djgpp AT delorie DOT com>
Subject: Re: make 3.78.1 check
In-Reply-To: <Pine.A32.3.96.1000124122411.59798B-100000@wilkes1.wilkes.edu>
Message-ID: <Pine.SUN.3.91.1000125094557.23222H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 24 Jan 2000, Frank Donahoe wrote:

> > It is by no means the last; stay tuned ;-).
> 
> Great! Thanks! But last above meant I'd worked my way through
> "diff," "grep," "gawk," "text utilities," and "texinfo" to "make."

I know.  But there are more up my sleeve ;-).

> > The only 2 peculiarities I can spot in the description of your system
> > is that (1) the DJGPP bin directory is after the Windows directories
> > in your PATH, and (2) I used the latest port of Perl (version 5.5.2,
> > available from SimTel.NET).
> 
> WINDOWS RULES!

Only if you let it do that ;-).

> How to prevent it from going first in PATH?

You can define a batch file that runs when the DOS box starts, and
replace the PATH in that batch file.

> Issue the command "echo --version" from the command prompt under DOS
> or BASH.  The result will be "--version" no matter which directory is
> first in PATH.  The shell runs the built-in command.

You need to type "c:\djg\bin\echo.exe --version".

Note that Make always looks along the PATH first, so it *will* call
the first echo.* executable it finds there, *before* falling back on
the builtin command of the shell.

Another idea to try is to invoke the test suite from COMMAND.COM (I
understand that you did that from Bash).

> > If the above doesn't help to resolve this, I'm afraid you'll have to
> > debug these specific tests and tell what you find.

I can only reiterate this last advice.  Insert debugging print
statements into the script and the Makefile it produces and take it
from there.