Date: Tue, 20 Jan 1998 20:11:36 -0500 (EST)
Message-Id: <199801210111.UAA22405@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: robert DOT hoehne AT gmx DOT net
CC: djgpp-workers AT delorie DOT com
In-reply-to: <34C3CFFE.F72F7C7@gmx.net> (message from Robert Hoehne on Mon, 19
	Jan 1998 23:13:18 +0100)
Subject: Re: gcc 2.8.0
Precedence: bulk


>   I would prefer this technique, but how to include the changes
>   for djggp.env in the gcc280b.zip? In the readme? Knowing
>   that there are people which cannot read them?

One thing I was thinking of adding to crt1 is the ability to have a
*file* named after the executable, like djgpp/envs/gcc, so that the
env file can be included in the zip file instead of in djgpp.env

Another option is to modify gcc.c to build an appropriate directory
(in addition to $EXEC_PREFIX - we probably want to replace the
/usr/local logic) based on the $DJDIR variable.

>   This will work OK with ld 2.8.1 but I don't know if it will work
>   also with ld 2.7 (I haven't it anymore, maybe someone can test it,
>   at least the --force-exe-suffix is unknown to it AFAIK)

*I* still use ld 2.7 (I'm lazy)

I'd prefer using djdev's specs, which use djdev's stubify, so that if
you install a new djdev, you get the new stub when you compile.