Date: Mon, 26 Jun 2000 08:27:35 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: ANNOUNCE: Binutils 2.10 released
In-Reply-To: <3955FFB9.7993.18D180@localhost>
Message-ID: <Pine.SUN.3.91.1000626082707.5330A-100000@is>
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 Sun, 25 Jun 2000, Mark E. wrote:

> > No, I thought that a future GCC distribution could come with specs
> > that already has -mbnu210 in it.  I don't think it's a good idea for
> > users to edit specs, I'm afraid they will screw it up.
> 
> What I don't understand is why include -mbnu210 in the specs?

So that people won't need to type it from the command line.  I
understand that everybody will want -mbnu210, right?

> The stub in the sources hasn't been updated. I'll post a patch to fix this 
> (assuming the hex stub in djgpp/src/stub/stub.h is ok to copy over and diff 
> against).

Perhaps it is better to modify the Binutils build process so that it
takes the stub directly from stubify.exe, if it is installed.