X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Tue, 17 May 2005 15:50:00 -0400
Message-Id: <200505171950.j4HJo06W009601@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <1116358470.973762.285250@g44g2000cwa.googlegroups.com>
	(ahmadwaris AT hotmail DOT com)
Subject: Re: Error compiling with djgpp: system cannot execute the command specified
References: <1116353987 DOT 906633 DOT 199670 AT o13g2000cwo DOT googlegroups DOT com>
   <200505171834 DOT j4HIY1bf007679 AT envy DOT delorie DOT com> <1116358470 DOT 973762 DOT 285250 AT g44g2000cwa DOT googlegroups DOT com>
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Thanks for the advice. Just out of curiosity - what is the reason
> for this behavior?

It's a limitation of the DOS API, so we can't directly fix it.  DJGPP
programs can call each other with longer command lines, using a custom
API, so using a Makefile basically avoids the DOS restriction by
reading the list of arguments from a file (the Makefile) then calling
gcc using DJGPP's API instead of the DOS API.

Alternately, you could list all the command line entries in a file,
and use the @file syntax:

	gcc @objects.lst

But Makefiles are useful for other reasons too.