From: Nathanael Nerode <neroden@twcny.rr.com>
To: newlib@sources.redhat.com, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com, gcc-patches@sources.redhat.com,
dj@redhat.com
Subject: Patch: drop NEC v810 support
Date: Sun, 10 Nov 2002 16:10:00 -0000 [thread overview]
Message-ID: <20021111000953.GA526@doctormoo> (raw)
After some investigation, it looks like v810 isn't really supported by any
subdirectory of gcc or src. The only one with any code for it is newlib,
I can't find any evidence that anyone's using it or that it works, and it
hasn't been updated since 1995.
Its configury fragment, toplevel config/mt-v810, is causing me trouble in
autoconfiscation. Therefore, this patch simply blows the target away.
If anyone is actually using newlib for the NEC v810, I expect them to tell
me how, so I can make some configury which is more reasonable than the
current one.
* configure.in (v810*): Remove support.
--- configure.in 2002-11-10 18:58:13.000000000 -0500
+++ configure.in.new 2002-11-10 18:57:40.000000000 -0500
@@ -608,9 +608,6 @@
;;
sparc-*-solaris* | sparc64-*-solaris* | sparcv9-*-solaris*)
;;
- v810-*-*)
- noconfigdirs="$noconfigdirs bfd binutils gas gcc gdb ld ${libstdcxx_version} opcodes target-libgloss ${libgcj}"
- ;;
v850-*-*)
noconfigdirs="$noconfigdirs target-libgloss ${libgcj}"
;;
@@ -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"
;;
next reply other threads:[~2002-11-11 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 16:10 Nathanael Nerode [this message]
2002-11-11 8:55 ` Jim Wilson
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=20021111000953.GA526@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.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