Date:	Thu, 27 Mar 1997 13:31:36 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"Sean L. Palmer" <spalmer AT pobox DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Rhide:long command lines problem
In-Reply-To:	<01bc3a1e$957601a0$ee0b1d26@ghost.artnet.net>
Message-ID:	<Pine.SUN.3.91.970327133108.9299S-100000@is>
MIME-Version:	1.0

On 26 Mar 1997, Sean L. Palmer wrote:

> I JUST NOW DOWNLOADED v2.01, RHIDE1.2, Make 3.75.  I have never before used
> DJGPP, so mixing is not an issue.
> 
> I have about 300 files that need to be compiled. I put them all in the
> project and do a build, and voila I get "Command line too long" in the info
> window back.
> 
> Now what?  Is the command line too long for Windows 95?

No, DJGPP doesn't rely on the OS to pass long command lines, because
of arbitrary limits these impose.  Rhide invokes Make to build your
program, and Make passes command lines to Gcc and other DJGPP tools in
a way that allows command lines be upto 13KB long; I don't think you
have exceeded that limit, have you?  (If you want to know more about
these issues, I suggest you read sections 16.4 and 16.5 of the DJGPP
FAQ list, and the documentation of functions `system' and `spawn*' in
the libc reference.)

Your problem might be caused by something in your PATH setting which
prevents Make from finding a program it needs to invoke (most
probably, gcc.exe itself).  When this happens, Make assumes that the
missing program is actually an internal DOS command, and will try to
call COMMAND.COM to execute it; but if the line is too long for
COMMAND.COM to handle, it will print the message "Command line too
long" and fail.

So please see whether there's something wrong with your PATH, or
whether gcc.exe is in your bin subdirectory of the main DJGPP
directory.

- Raw text -