Date:	Sun, 2 May 1999 11:10:28 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andris Pavenis <pavenis AT lanet DOT lv>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: v2.03: wrapping up
In-Reply-To:	<B0000085469@stargate.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.990502110955.563D-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 30 Apr 1999, Andris Pavenis wrote:

> After that I can try to patch affected packages, build them and send patches 
> if success. As I said there are not so many. Of course we still have packages
> that are not yet released.

I suggested using built-in expansion of environment variables in the
library, and using that feature to put -imacros option into the specs
file that goes with the compiler distribution.  I also posted code
that implements that.

Please tell if you think this is an okay solution for the problem,
which will alow to remove lib/specs from djdev203.zip.

If you don't like this solution either, please explain what are its
aspects that you don't like, and I will try to think how to solve
those difficulties.

I would like to find a solution that allows programmers to use
__DJGPP__ and __DJGPP_MINOR__ without restrictions.  If such a
solution is possible (I think it is), it should be better than any
patch to the DJGPP ports, because it will instantly solve any problems
with those ports, and also all the potential problems in the future.
It will also allow to release DJGPP v2.03 sooner.

- Raw text -