Message-ID:	<8D53104ECD0CD211AF4000A0C9D60AE34C59B4@probe-2.acclaim-euro.net>
From:	Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	djgpp AT delorie DOT com
Subject:	RE: problems compiling allegro
Date:	Wed, 3 Feb 1999 17:33:18 -0000
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.0.1460.8)
Reply-To:	djgpp AT delorie DOT com

> Eli Zaretskii writes:
>> My #1 guess is that there is something very strange 
>> about your echo command: do you have any strange aliases or other 
>> software installed that could be changing the way this behaves? 
>> (make should be using the echo.exe from djgpp/bin).
>
> There's no echo.exe in v2.02: by popular demand it was renamed into 
> djecho.exe.

Really? That is useful to know :-) There still shouldn't be any 
problems, though: I've built Allegro successfully with djgpp 2.02, 
which will presumably be using the internal command.com echo. The 
only incompatibility is that trying to echo an empty string will 
produce that stupid "echo is off" message from command.com, but 
this only happens in one place early on in the MMX-assembler 
test, and anyone who has djgpp 2.02 will presumably also have an 
MMX-aware version of binutils, so this ought not to be a problem.

To the original poster, my comments still stand: do you have any 
odd aliases set up for your echo command?


	Shawn Hargreaves.

- Raw text -