Date: Thu, 27 Aug 92 12:43:23 CDT
From: "George Jetson" <pynq AT midway DOT uchicago DOT edu>
To: dj AT athena DOT ctron DOT com
Subject: Re:  gcc environment variables
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

You wrote (in response to query about implementation of a GCC.CFG file) :

>Since FSF writes gcc, and they use Unix, I doubt they would be willing
>to make this change.  However, you can increase the amount of
>environment space with config.sys.

I take it by this that you mean that the use of environment variables is
threaded throughout the code and it is thus not just a matter of
setting up internal variables in GO32 a little differently.  Correct?

Nevertheless, it would be a simple matter to change GO32 to read from a
file and set the env vars accordingly, such that all further processes
would see them in the env.

Of course, it would also be a simple matter to write a wrapper that
would do this and then call GO32.  Maybe I'll do that...

Now that I think about it, the right place to do this is in STUB.C
Expect to see a new version of STUB.EXE posted shortly.
(I am assuming that GCC.EXE is itself a STUB'd application)

>You could always recompile gcc so that the defaults match your
>directory structure (I think the default is /usr/local/lib/something).

Yes, but that would defeat the whole purpose...

Also, it occurs to me that the downside of people doing stuff for free
is that they feel free to do it however they want to, even if it is
wrong.  (I am, 50% [at least] kiddingly, talking about FSF here...)