X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Mon, 30 Nov 2020 20:18:49 +0200
Message-Id: <83a6uyk8s6.fsf@gnu.org>
From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
In-Reply-To: <eefd29fe-8e4d-9847-0b63-cc6220304679@iki.fi> (djgpp@delorie.com)
Subject: Re: __STRICT_ANSI__ and excluded definitions
References: <eefd29fe-8e4d-9847-0b63-cc6220304679 AT iki DOT fi>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> Date: Mon, 30 Nov 2020 19:40:50 +0200
> 
> Noticed that I'm failing to build recent GIT version of GCC for DJGPP due to different 
> interpretation of presence of macro __STRICT_ANSI__=1 in Linux and DJGPP

Why is __STRICT_ANSI__ important for _building_ GCC?  Does the build
use some compiler switch that forces __STRICT_ANSI__?