Date:	Fri, 22 Dec 2000 11:36:43 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<2593-Fri22Dec2000113643+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
In-reply-to:	<91tnie$mq2$1@nnrp1.deja.com> (dcasale@my-deja.com)
Subject:	Re: "Command line too long"
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1001219134418 DOT 365O-100000 AT is> <91tnie$mq2$1 AT nnrp1 DOT deja DOT com>
Reply-To:	djgpp AT delorie 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

> From: dcasale AT my-deja DOT com
> Newsgroups: comp.os.msdos.djgpp
> Date: Thu, 21 Dec 2000 20:01:23 GMT
>
> > > After some code changes and after installing some additional
> > > packages for DJGPP, I tried compiling the latest version of my
> > > compression program in RHIDE only to receive a "Command line too
> > > long" error.
> > >
> > > What might cause this?
> >
> > I'm guessing that some package you installed changed PATH, so now some
> > of the programs invoked by RHIDE doesn't support the special way of
> > passing long command lines between DJGPP programs.  (For details about
> > this special way, see section 16.4 of the FAQ.)  Section 16.6 of the
> > FAQ mentions, near its end, possible problems like that.
> 
> Interesting.  Especially since this problem cropped up when using
> _RHIDE_, not calling MAKE directly.

The problem can appear whenever any DJGPP program calls any other
program.  It is not limited to RHIDE.

> Well, the offender was a program which modified my AUTOEXEC.BAT by
> adding a bunch of extra, unneccessary environment variables.  With
> these extra environment variables loaded, RHIDE refused to run, even
> when attempting to compile code that had successfully compiled before.

Weird.  Can you tell what variables were those, and what their values
were?

> I don't quite understand why this is a problem, unless RHIDE was
> attempting to set an environment variable and failing because of lack
> of room.

This cannot happen, unless the total size of the environment was
approaching 16KB.

- Raw text -