This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Patch: drop NEC v810 support
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: Jim Wilson <wilson at redhat dot com>
- Cc: newlib at sources dot redhat dot com, binutils at sources dot redhat dot com, gdb-patches at sources dot redhat dot com, gcc-patches at sources dot redhat dot com, dj at redhat dot com
- Date: Mon, 11 Nov 2002 16:00:55 -0500
- Subject: Re: Patch: drop NEC v810 support
- References: <20021111000953.GA526@doctormoo> <xwulm40gi7e.fsf@tonopah.toronto.redhat.com>
Jim Wilson wrote:
It was a newlib only port, using the NEC compiler. It was a rather unusual
port, and one that we don't need to worry about now. Dropping the mt-v810
file is OK.
So if I submitted a patch which just did this, it could get approved easily?
* configure.in (v810*): Remove special setting of tools.
--- configure.in 2002-11-10 18:58:13.000000000 -0500
+++ configure.in.new 2002-11-10 18:57:40.000000000 -0500
@@ -1111,9 +1108,6 @@
extra_arflags_for_target=
extra_nmflags_for_target=
case "${target}" in
- v810*)
- target_makefile_frag="config/mt-v810"
- ;;
i[3456]86-*-netware*)
target_makefile_frag="config/mt-netware"
;;
Dropping the port is OK too, but if we are doing that, then we may as well
delete the newlib bits. The main part is in the lib/sys/sysnec810 directory
and the newlib configure.host file, but there are various files with
#ifdef __v810__ in them to deal with NEC compiler specific issues. Use
"find . -type f | xargs grep v810" to find them. This isn't your problem
though, it is a problem for the newlib maintainers to worry about.
Jim
I just want to get through the autoconfiscation blockers.
--Nathanael