From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: (toplevel patch) Use canonical names for target_subdir, build_subdir.
Date: Fri, 24 Jan 2003 03:41:00 -0000 [thread overview]
Message-ID: <20030124034053.GA22615@doctormoo> (raw)
Use the canonical build and target names for build_subdir and target_subdir.
This saves a tedious amount of work when we get around to autoconf 2.5x
conversion (where build_alias and target_alias may be empty strings).
Built successfully on i686-pc-linux-gnu. (But then, this should make no
difference at all in the native case.)
Built combined tree cross to i386-cygwin, and one to powerpc-linux.
They worked as well as they did before.
Did as much other testing as I could with the tremendous unreliability of
out-of-the-box cross builds.
This was an easy change to make, and a pain in the neck to test, due to
general breakage for crosses in src.
I wouldn't mind additional testing by people better at it than me. I
think I got everything which needs to change, but I'm not 100% sure.
(top level)
* configure.in: Use canonical names for build_subdir, target_subdir.
* configure: Regenerate.
(gcc)
* configure.in: Use canonical names for build_subdir, target_subdir.
* configure: Regenerate.
(gdb)
* configure.in: Use canonical name for target_subdir.
* configure: Regenerate.
Note that this doesn't always like to apply as a single 'patch'; it's usually
happier as three.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.216
diff -u -r1.216 configure.in
--- configure.in 23 Jan 2003 22:32:25 -0000 1.216
+++ configure.in 23 Jan 2003 22:43:58 -0000
@@ -201,7 +201,7 @@
# We always want to use the same name for this directory, so that dejagnu
# can reliably find it.
-target_subdir=${target_alias}
+target_subdir=${target}
if test ! -d ${target_subdir} ; then
if mkdir ${target_subdir} ; then true
@@ -211,8 +211,7 @@
fi
fi
-build_prefix=build-
-build_subdir=${build_prefix}${build_alias}
+build_subdir=build-${build}
if test x"${build_alias}" != x"${host}" ; then
if test ! -d ${build_subdir} ; then
Index: gcc/configure.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/configure.in,v
retrieving revision 1.637
diff -u -r1.637 configure.in
--- gcc/configure.in 21 Jan 2003 13:45:07 -0000 1.637
+++ gcc/configure.in 23 Jan 2003 22:44:09 -0000
@@ -1028,7 +1028,7 @@
cd ..
rm -rf $tempdir
build_auto=auto-build.h
- FORBUILD=../build-$build_alias
+ FORBUILD=../build-$build
fi
AC_SUBST(FORBUILD)
@@ -2712,7 +2712,7 @@
host_canonical=${host}
target_subdir=
if test "${host}" != "${target}" ; then
- target_subdir=${target_alias}/
+ target_subdir=${target}/
fi
AC_SUBST(build_canonical)
AC_SUBST(host_canonical)
Index: gdb/configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.118
diff -u -r1.118 configure.in
--- gdb/configure.in 22 Jan 2003 23:50:35 -0000 1.118
+++ gdb/configure.in 23 Jan 2003 22:44:27 -0000
@@ -1204,7 +1204,7 @@
# target_subdir is used by the testsuite to find the target libraries.
target_subdir=
if test "${host}" != "${target}"; then
- target_subdir="${target_alias}/"
+ target_subdir="${target}/"
fi
AC_SUBST(target_subdir)
next reply other threads:[~2003-01-24 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:41 Nathanael Nerode [this message]
2003-01-24 16:51 ` Alexandre Oliva
2003-01-24 18:32 ` Nathanael Nerode
2003-01-24 19:16 ` Alexandre Oliva
2003-01-26 12:22 ` Phil Edwards
2003-01-26 12:45 ` Alexandre Oliva
2003-01-27 14:56 ` Phil Edwards
2003-01-27 15:26 ` Phil Edwards
2003-01-25 0:56 ` Andreas Schwab
2003-01-25 21:27 ` Phil Edwards
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=20030124034053.GA22615@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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