[patch bfd] Mark sh5*-*-* and sh64*-*-* as obsolete (Was: Re: New failures with .debug_ranges test)
Jan-Benedict Glaw
jbglaw@lug-owl.de
Thu Jan 28 00:15:00 GMT 2016
On Sat, 2015-12-05 09:06:27 +0900, Kaz Kojima <kkojima@rr.iij4u.or.jp> wrote:
> Nick Clifton <nickc@redhat.com> wrote:
> >> I guess that now we have no reason to keep sh5/sh64 targets.
> >
> > You are the SH maintainer, so if you are happy to mark these targets
> > as obsolete please update bfd/config.bfd.
>
> OK, I'd like to apply the following patch in 48 hours if there is
> no objection. It's tested with and without --enable-obsolete.
The GCC port still builds sh64-linux without --enable-obsolete. I
think you'd obsolete it in gcc/config.gcc as well, and update
contrib/config_list.mk by adding OPT-enable-obsolete where
appropriate. That way, my build robot can catch up to supply that flag
and build that target (until it finally gets removed.)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: The course of history shows that as a government grows, liberty
the second : decreases." (Thomas Jefferson)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <https://sourceware.org/pipermail/binutils/attachments/20160128/bd7f53cc/attachment.sig>
More information about the Binutils
mailing list