From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com, Laurynas Biveinis <lauras AT softhome DOT net>
Subject: Re: 2.03 vs 3.2
Date: Wed, 16 Oct 2002 07:08:06 +0300
User-Agent: KMail/1.4.7
References: <51168290418 DOT 20021014163221 AT softhome DOT net> <29272946195 DOT 20021015213637 AT softhome DOT net>
In-Reply-To: <29272946195.20021015213637@softhome.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1257"
Content-Disposition: inline
Message-Id: <200210160708.06643.pavenis@latnet.lv>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9G483H13959
Reply-To: djgpp-workers AT delorie DOT com

On Tuesday 15 October 2002 22:36, Laurynas Biveinis wrote:
> > FYI, I'm slowly making my way to get 2.03 compile without warnings. I've
> > backported lots of IMO safe patches from 2.04.
>
> Well, I'm sort of done with it. Below is the patch. All of djdev
> builds with -Werror. I'm not going to backport further fixes, as I've
> already spent too much time working on it. Troubles like bzero
> do not concern me much - I'm happy with this patch for my personal use :)
>
> Anyway here it is FYI:
>
> - Use djgpp-x.djl

Don't do so.

I intentionally changed the name to be able to use a different linker script 
but not one provided by djdev. Perhaps the best is simply to make this script 
compatible with new GCC versions. If all will be Ok for
some time (perhaps one year or something about that) we could maybe
stop providing a linker script with GCC. However seems that gcc-3.3 will again
require changes. We can only hope that things will stabilize later.

Andris