From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com
Subject: [patch] target makefile frag collection, REALLY correct.
Date: Tue, 02 Jul 2002 12:44:00 -0000 [thread overview]
Message-ID: <20020702193927.GA18968@doctormoo.dyndns.org> (raw)
Of course, my previous version was wrong. Here's the really final version.
(ick)
2002-07-02 Nathanael Nerode <neroden@gcc.gnu.org>
* configure.in: Rearrange target Makefile fragment collection.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.166
diff -u -r1.166 configure.in
--- configure.in 2 Jul 2002 18:01:37 -0000 1.166
+++ configure.in 2 Jul 2002 19:39:07 -0000
@@ -1178,44 +1178,47 @@
case "${target}" in
v810*)
- target_makefile_frag="${target_makefile_frag} config/mt-v810"
+ target_makefile_frag="config/mt-v810"
;;
i[3456]86-*-netware*)
- target_makefile_frag="${target_makefile_frag} config/mt-netware"
+ target_makefile_frag="config/mt-netware"
;;
powerpc-*-netware*)
- target_makefile_frag="${target_makefile_frag} config/mt-netware"
- ;;
- alpha*-*-linux*)
- target_makefile_frag="${target_makefile_frag} config/mt-linux"
- target_makefile_frag="${target_makefile_frag} config/mt-alphaieee"
- ;;
- alpha*-*-*)
- target_makefile_frag="${target_makefile_frag} config/mt-alphaieee"
+ target_makefile_frag="config/mt-netware"
;;
*-*-linux*)
- target_makefile_frag="${target_makefile_frag} config/mt-linux"
+ target_makefile_frag="config/mt-linux"
;;
*-*-aix4.[3456789]* | *-*-aix[56789].*)
- target_makefile_frag="${target_makefile_frag} config/mt-aix43"
+ target_makefile_frag="config/mt-aix43"
;;
mips*-*-pe | sh*-*-pe | *arm-wince-pe)
- target_makefile_frag="${target_makefile_frag} config/mt-wince"
+ target_makefile_frag="config/mt-wince"
+ ;;
+esac
+
+alphaieee_frag=
+case $target in
+ alpha*-*-*)
+ # This just makes sure to use the -mieee option to build target libs.
+ # This should probably be set individually by each library.
+ alphaieee_frag="config/mt-alphaieee"
;;
esac
# If --enable-target-optspace always use -Os instead of -O2 to build
# the target libraries, similarly if it is not specified, use -Os
# on selected platforms.
+ospace_frag=
case "${enable_target_optspace}:${target}" in
yes:*)
- target_makefile_frag="${target_makefile_frag} config/mt-ospace"
+ ospace_frag="config/mt-ospace"
;;
:d30v-*)
- target_makefile_frag="${target_makefile_frag} config/mt-d30v"
+ ospace_frag="config/mt-d30v"
;;
:m32r-* | :d10v-* | :fr30-*)
- target_makefile_frag="${target_makefile_frag} config/mt-ospace"
+ ospace_frag="config/mt-ospace"
;;
no:* | :*)
;;
@@ -1225,8 +1228,8 @@
esac
rm -f mt-frag
-if test -n "${target_makefile_frag}" ; then
- for f in ${target_makefile_frag}
+if test -n "${target_makefile_frag}${alphaieee_frag}${ospace_frag}" ; then
+ for f in ${target_makefile_frag} ${alphaieee_frag} ${ospace_frag}
do
cat ${srcdir}/$f >> mt-frag
done
next reply other threads:[~2002-07-02 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 12:44 Nathanael Nerode [this message]
2002-07-02 14:28 ` DJ Delorie
2002-07-02 14:57 ` Matt Kraai
2002-07-02 14:45 ` Matt Kraai
2002-07-02 15:24 ` DJ Delorie
2002-07-02 16:47 ` 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=20020702193927.GA18968@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