From: Jim Wilson <wilson@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: newlib@sources.redhat.com, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com, gcc-patches@sources.redhat.com,
dj@redhat.com
Subject: Re: Patch: drop NEC v810 support
Date: Mon, 11 Nov 2002 08:55:00 -0000 [thread overview]
Message-ID: <xwulm40gi7e.fsf@tonopah.toronto.redhat.com> (raw)
In-Reply-To: <20021111000953.GA526@doctormoo>
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.
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
next prev parent reply other threads:[~2002-11-11 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 16:10 Nathanael Nerode
2002-11-11 8:55 ` Jim Wilson [this message]
2002-11-11 17:15 ` Nathanael Nerode
2002-11-11 17:15 ` Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xwulm40gi7e.fsf@tonopah.toronto.redhat.com \
--to=wilson@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=newlib@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox