Message-ID:	<000e01be5067$ca4ab5e0$1e2d87ca@default>
From:	"Maki Yoshimura" <maki DOT mail AT ibm DOT net>
To:	<djgpp AT delorie DOT com>
Subject:	RE: Using GNU make with DOS compiler causes DOS MODE popup
Date:	Fri, 5 Feb 1999 02:56:45 +0900
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
X-MIME-Autoconverted:	from 8bit to quoted-printable by out5.ibm.net id RAA97468
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id MAA10646
Reply-To:	djgpp AT delorie DOT com

Please do not send these kinds of message.
I do not understand English language !

-----Original Message-----
差出人 : Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
宛先 : Lee Marzke <tallyho AT voicenet DOT com>
CC : djgpp AT delorie DOT com <djgpp AT delorie DOT com>
日時 : 1999年2月5日 2:47
件名 : Re: Using GNU make with DOS compiler causes DOS MODE popup


>
>On Wed, 3 Feb 1999, Lee Marzke wrote:
>
>> Two problems, first Line length is too long to enable
>> processing a list of files with a for loop. ( with command.com )
>
>If your for loop is too long, it won't work even from the command
>line, right?  So why did you expect Make to handle it correctly?
>
>The usual work-around for these cases is to break the list of files
>into two or more shorter lists, and have several for loops to process
>them.
>
>> To fix this,
>> I installed BASH, and now this works OK, but I have a new
>> strange problem.  Whenever bash calls the DOS compiler, after
>> the compiler exits, Windows complains with a popup screen
>> about "This program needs to be run in DOS mode"
>
>Which program does it complain about?  We need to know this info to
>advise you about the correct solutions.
>
>> This happes for each source file, so I get many of these
>> dialogs.   Is there some reason that GNU make can't call
>> DOS programs ?
>
>The DJGPP port of GNU Make has no problems calling DOS programs, I'm
>guessing that this problem happens because of some special setup of
>your system.  But please post the full details about the message
>popped by Windows (you didn't even tell which version of Windows is
>that).
>

- Raw text -