From: dcasale AT my-deja DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: "Command line too long"
Date: Thu, 21 Dec 2000 20:01:23 GMT
Organization: Deja.com
Lines: 60
Message-ID: <91tnie$mq2$1@nnrp1.deja.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1001219134418 DOT 365O-100000 AT is>
NNTP-Posting-Host: 199.249.234.30
X-Article-Creation-Date: Thu Dec 21 20:01:23 2000 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
X-Http-Proxy: 1.1 x58.deja.com:80 (Squid/1.1.22) for client 199.249.234.30
X-MyDeja-Info: XMYDJUIDdcasale
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 1001219134418 DOT 365O-100000 AT is>,
  djgpp AT delorie DOT com wrote:
>
> On Mon, 18 Dec 2000 dcasale AT my-deja DOT com wrote:
>
> > I _think_ I sent this before, but Dejanews says I didn't.  *shrugs*
>
> You did post it, at least 3 times.  There are propagation delays that
> you should account for before posting again.

The problem was that DejaNews was acting up.  Usually DejaNews
propagates within about five minutes.  It took at least four hours
(that's about when I stopped looking) for those posts to show up on my
end, which is why I was wondering.  Twice, DejaNews gave me an error
when I tried to send the post, but apparently it went through anyway.

In any case...woops.  Sorry about that.  ^^;;

> > 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.  See below.

> > What can I do about it?
>
> Find the offending program.
...
[snip]

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.

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.

Anyway, problem solved.  In case anyone has a problem like this again,
the first thing they should do is check for excess amounts of
environment variables.  :-)

Damon Casale, damon AT WRONG DOT redshift DOT com (remove the obvious)
"What do you mean, the environment's not able to support life?  It
looks a little crowded to me."


Sent via Deja.com
http://www.deja.com/