From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Thu, 8 Feb 2001 10:36:36 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: GCC: DJGPP bootstrap fix + define MSDOS
Message-ID: <3A8276B4.22740.2F391B@localhost>
In-reply-to: <3A82BDC5.12709.D7D88B@localhost>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010208102233 DOT 20284R-100000 AT is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
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

> It means that DJGPP port of gcc-3.0 will be no more usable with 
> binutils 2.8.* and 2.9.*. One will need to use 2.10 or above (really
> bnu2951b.zip will also work)

I agree with Andris that -mbnu210 can probably be removed even without the 
bootstrap failure forcing the issue.

A gcc 3.0 binary built using binutils 2.10 won't work if you install it on a 
machine with binutils < 2.10. But a gcc 3.0 binary can still be built using 
binutils < 2.10 (or 2.951), it just won't be able to take advantage of weak 
symbols, etc. that makes the C++ problems with static data members go away.

Two binaries could be distributed. One built using bnu 2.10 or later, and the 
other built using bnu 2.91, but that would probably confuse rather than help. 

Mark