Date: Thu, 27 Aug 92 13:51:58 EDT
From: DJ Delorie <dj AT athena DOT ctron DOT com>
To: pynq AT midway DOT uchicago DOT edu
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:  gcc environment variables

>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?

gcc and cccp call getenv() directly.  GO32 has nothing to do with it.

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

go32 is low on code space, so additions need to be quite important
before they can get in.

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

Or a batch file?

>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)

Please do NOT modify stub.exe.  It needs to be as small and simple as
possible to fulfill it's function.

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

You could always rearrange your directories to match the defaults.

>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...)

Or to not do it at all.  They do, however, accept volunteers and
contributions.

DJ
dj AT ctron DOT com
Life is a banana.