From: Nathanael Nerode <neroden@twcny.rr.com>
To: gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
gcc-patches@gcc.gnu.org, rda@sources.redhat.com
Subject: (committed toplevel patch) Make rda native-only
Date: Thu, 23 Jan 2003 19:57:00 -0000 [thread overview]
Message-ID: <20030123195700.GA6360@doctormoo> (raw)
RDA doesn't build properly in cross configurations, which is screwing up
my tests of the rest of the tree whenever the rda directory is avaialbe.
I'm committing this as obvious.
* configure.in: Make rda native-only.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.214
diff -u -r1.214 configure.in
--- configure.in 19 Jan 2003 23:44:27 -0000 1.214
+++ configure.in 23 Jan 2003 19:51:26 -0000
@@ -258,7 +257,7 @@
# Some tools are only suitable for building in a "native" situation.
# Remove these if host!=target.
-native_only="autoconf automake libtool fileutils find gawk gettext grep gzip hello indent m4 rcs recode sed shellutils tar textutils uudecode wdiff gprof target-groff guile perl time ash bash bzip2 prms snavigator gnuserv target-gperf"
+native_only="autoconf automake libtool fileutils find gawk gettext grep gzip hello indent m4 rcs recode sed shellutils tar textutils uudecode wdiff gprof target-groff guile perl time ash bash bzip2 prms snavigator gnuserv target-gperf target-rda"
# Similarly, some are only suitable for cross toolchains.
# Remove these if host=target.
next reply other threads:[~2003-01-23 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 19:57 Nathanael Nerode [this message]
2003-01-23 21:37 ` Alexandre Oliva
2003-01-23 22:04 Nathanael Nerode
2003-01-23 23:38 ` Alexandre Oliva
2003-01-23 22:09 Nathanael Nerode
2003-01-23 22:15 ` DJ Delorie
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=20030123195700.GA6360@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).