From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gcc compiler from djgpp
Date: Wed, 16 Apr 2003 08:30:53 CDT
Organization: Rice University, Houston, TX
Lines: 26
Message-ID: <3e9d5b0d.sandmann@clio.rice.edu>
References: <3e90e080 DOT sandmann AT clio DOT rice DOT edu> <3E919B6D DOT 9010805 AT lml DOT ls DOT fi DOT upm DOT es> <b9445ce8 DOT 0304111000 DOT 16487441 AT posting DOT google DOT com>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1050500016 21638 128.42.105.3 (16 Apr 2003 13:33:36 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: Wed, 16 Apr 2003 13:33:36 +0000 (UTC)
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Thanks for all the ideas, I got it to work but only in the command
> (not cmd) window. The compiled program will also only run when run
> from the command window.

> Is that expected and does it narrow down the problem?

Not expected, but interesting.  On one of my systems I had to
remove lots of environment variables to get it work reliably 
doing makes - maybe this is the problem you are seeing.  I know
I had to remove "SHELL" which was set by some other software.

I ended up with a CMD procedure to clear lots of environment
variables, which made that window work fine with DJGPP.

> Is there a way to kill all EVs for one CMD window so I can reset them
> to only the things I want to run GCC?

I just did a SET > SMALLENV.CMD, then edited it to have lots lof lines
that looked like:
set SHELL=
set TERM=
set TERMCAP=
set TERMINFO=
set DISPLAY=

I explicitly set the path to a much shorter version also.