Date: Sat, 12 May 2001 19:01:20 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: DJ Delorie <dj AT delorie DOT com>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: [PATCH] Update to compiler options for DJGPP CVS version
In-Reply-To: <200105121438.KAA12646@envy.delorie.com>
Message-ID: <Pine.A41.4.05.10105121833320.39122-100000@ieva06.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Sat, 12 May 2001, DJ Delorie wrote:

> 
> > - removed -traditional. -traditional is becoming nuisance with gcc-3.0
> 
> Can you give specific examples of the problems it causes?
> 

Some time ago (perhaps 15 March CVS version) I got large number of
additional warnings we would have to deal with. As I remeber I posted
information about this in djgpp-workers list. Now it seems that I'm not
able to get it really working at all both for DJGPP and Linux with
gcc-3.0 and 3.1 development versions.

To get it not compaining about command line parameters I had now to
eliminate -remap and -imacros ... from cpp specs when -traditional is
being used (like %{!traditional:-remap}). The latest one is significant
for DJGPP as it's used to get macros __DJGPP__, __DJGPP_MINOR__

Maybe it's really not worth to mess with -traditional any more.

Andris