From: Anthony Liguori <aliguori@cs.utexas.edu>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Improve gcc 3 checking
Date: Mon, 18 Dec 2006 21:23:32 -0600 [thread overview]
Message-ID: <45875B34.7080802@cs.utexas.edu> (raw)
In-Reply-To: <200612190309.20174.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
Paul Brook wrote:
>> If they explicitly specific an invalid --cc=, the checks will get
>> triggered (but in the past, we would have bailed).
>>
>
> That's what I'm objecting to. If I do:
>
> ./configure --cc=gcc4
>
> I expect configure to either use gcc4 or fail with an error. Preferably the
> latter, but I'm open to persuasion.
>
> I don't want configure to decide it knows better and use gcc3 anyway.
>
Okay, it now will throw an error if you specify --cc=gcc4.
Regards,
Anthony Liguori
> Paul
>
[-- Attachment #2: qemu-gcc-3x.diff --]
[-- Type: text/x-patch, Size: 2354 bytes --]
diff -r f928121a13c1 configure
--- a/configure Mon Dec 18 20:29:34 2006 -0600
+++ b/configure Mon Dec 18 21:20:36 2006 -0600
@@ -22,6 +22,8 @@ static="no"
static="no"
cross_prefix=""
cc="gcc"
+gcc3_check="yes"
+gcc3_list="gcc-3.4 gcc34 gcc-3.3 gcc33 gcc-3.2 gcc32"
host_cc="gcc"
ar="ar"
make="make"
@@ -178,6 +180,7 @@ for opt do
--cross-prefix=*) cross_prefix="$optarg"
;;
--cc=*) cc="$optarg"
+ gcc3_check="no"
;;
--host-cc=*) host_cc="$optarg"
;;
@@ -311,6 +314,45 @@ if test "$mingw32" = "yes" ; then
oss="no"
if [ "$cpu" = "i386" ] ; then
kqemu="yes"
+ fi
+fi
+
+# Check for gcc4, error if pre-gcc4
+if test "$check_gcc" = "yes" ; then
+ cat > $TMPC <<EOF
+#if __GNUC__ < 4
+#error gcc3
+#endif
+int main(){return 0;}
+EOF
+ check_cc() {
+ which "$1" >&/dev/null
+ return $?
+ }
+
+ if "$cc" -o $TMPE $TMPC 2>/dev/null ; then
+ echo "WARNING: \"$cc\" looks like gcc 4.x"
+ found_compat_cc="no"
+ if test "$gcc3_check" = "yes" ; then
+ echo "Looking for gcc 3.x"
+ for compat_cc in $gcc3_list ; do
+ if check_cc "$compat_cc" ; then
+ echo "Found \"$compat_cc\""
+ cc="$compat_cc"
+ found_compat_cc="yes"
+ break
+ fi
+ done
+ if test "$found_compat_cc" = "no" ; then
+ echo "gcc 3.x not found!"
+ fi
+ fi
+ if test "$found_compat_cc" = "no" ; then
+ echo "QEMU is known to have problems when compiled with gcc 4.x"
+ echo "It is recommended that you use gcc 3.x to build QEMU"
+ echo "To use this compiler anyway, configure with --disable-gcc-check"
+ exit 1;
+ fi
fi
fi
@@ -414,23 +456,6 @@ have_gcc3_options="no"
have_gcc3_options="no"
if $cc -fno-reorder-blocks -fno-optimize-sibling-calls -o $TMPO $TMPC 2> /dev/null ; then
have_gcc3_options="yes"
-fi
-
-# Check for gcc4, error if pre-gcc4
-if test "$check_gcc" = "yes" ; then
- cat > $TMPC <<EOF
-#if __GNUC__ < 4
-#error gcc3
-#endif
-int main(){return 0;}
-EOF
- if $cc -o $TMPO $TMPC 2>/dev/null ; then
- echo "ERROR: \"$cc\" looks like gcc 4.x"
- echo "QEMU is known to have problems when compiled with gcc 4.x"
- echo "It is recommended that you use gcc 3.x to build QEMU"
- echo "To use this compiler anyway, configure with --disable-gcc-check"
- exit 1;
- fi
fi
##########################################
prev parent reply other threads:[~2006-12-19 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 2:25 [Qemu-devel] [PATCH] Improve gcc 3 checking Anthony Liguori
2006-12-19 2:31 ` Paul Brook
2006-12-19 2:58 ` Anthony Liguori
2006-12-19 3:09 ` Paul Brook
2006-12-19 3:23 ` Anthony Liguori [this message]
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=45875B34.7080802@cs.utexas.edu \
--to=aliguori@cs.utexas.edu \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).