From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc-patches@gcc.gnu.org
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
dj@redhat.com
Subject: toplevel configure.in: small rearrangement
Date: Fri, 20 Sep 2002 13:19:00 -0000 [thread overview]
Message-ID: <20020920201545.GA22355@doctormoo.dyndns.org> (raw)
I'm back.
This moves one of the definitions of CC a bit lower; when I autoconfiscate,
it's much easier if all the logic related to CC is as close as possible, and
also if all the fragment collection code is uninterrupted by other things.
Tested, no behavior changes.
2002-09-20 Nathanael Nerode
* configure.in: Rearrange.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.177
diff -u -3 -r1.177 configure.in
--- configure.in 19 Aug 2002 20:38:15 -0000 1.177
+++ configure.in 20 Sep 2002 20:10:30 -0000
@@ -1127,25 +1127,6 @@
host_makefile_frag=mh-frag
fi
-# If we aren't going to be using gcc, see if we can extract a definition
-# of CC from the fragment.
-# Actually, use the 'pre-extracted' version above.
-if test -z "${CC}" && test "${build}" = "${host}" ; then
- IFS="${IFS= }"; save_ifs="$IFS"; IFS="${IFS}:"
- found=
- for dir in $PATH; do
- test -z "$dir" && dir=.
- if test -f $dir/gcc; then
- found=yes
- break
- fi
- done
- IFS="$save_ifs"
- if test -z "${found}" && test -n "${tentative_cc}" ; then
- CC=$tentative_cc
- fi
-fi
-
case "${target}" in
v810*)
target_makefile_frag="config/mt-v810"
@@ -1281,6 +1262,25 @@
withoptions="$withoptions -x-libraries=/usr/lib/pa20_64 -x-includes=/usr/X11R6/include"
;;
esac
+
+# If we aren't going to be using gcc, see if we can extract a definition
+# of CC from the fragment.
+# Actually, use the 'pre-extracted' version above.
+if test -z "${CC}" && test "${build}" = "${host}" ; then
+ IFS="${IFS= }"; save_ifs="$IFS"; IFS="${IFS}:"
+ found=
+ for dir in $PATH; do
+ test -z "$dir" && dir=.
+ if test -f $dir/gcc; then
+ found=yes
+ break
+ fi
+ done
+ IFS="$save_ifs"
+ if test -z "${found}" && test -n "${tentative_cc}" ; then
+ CC=$tentative_cc
+ fi
+fi
# post-target:
next reply other threads:[~2002-09-20 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 13:19 Nathanael Nerode [this message]
2002-09-20 13:45 ` 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=20020920201545.GA22355@doctormoo.dyndns.org \
--to=neroden@doctormoo.dyndns.org \
--cc=binutils@sources.redhat.com \
--cc=dj@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