All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] Improve gcc 3 checking
Date: Mon, 18 Dec 2006 20:58:32 -0600	[thread overview]
Message-ID: <45875558.7020501@cs.utexas.edu> (raw)
In-Reply-To: <200612190231.08331.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Paul Brook wrote:
> On Tuesday 19 December 2006 02:25, Anthony Liguori wrote:
>   
>> +gcc3_list="gcc32 gcc33 gcc34 gcc-3.2 gcc-3.3 gcc-3.4"
>>     
>
> Shouldn't we be preferring newer compilers?
>   

Attached patch changes order plus improves the initial GCC 4 check a bit.

>> +       echo "Looking for gcc 3.x"
>>     
>
> We shouldn't do this if if the user explicitly specified a compiler.
> Replacing explicit user setting with guesses is bad.
>   

This stuff kicks in only if the user doesn't specific 
--disable-gcc-check and CC is not GCC 4.

So if the user specific a valid --cc=, then this check won't get triggered.

If they explicitly specific an invalid --cc=, the checks will get 
triggered (but in the past, we would have bailed).

So, if the user wants to explicitly specify a compiler, they can happily 
do that.

Regards,

Anthony Liguori


> Paul
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>   


[-- Attachment #2: qemu-gcc-3x.diff --]
[-- Type: text/x-patch, Size: 2047 bytes --]

diff -r f928121a13c1 configure
--- a/configure	Mon Dec 18 20:29:34 2006 -0600
+++ b/configure	Mon Dec 18 20:54:20 2006 -0600
@@ -22,6 +22,7 @@ static="no"
 static="no"
 cross_prefix=""
 cc="gcc"
+gcc3_list="gcc-3.4 gcc34 gcc-3.3 gcc33 gcc-3.2 gcc32"
 host_cc="gcc"
 ar="ar"
 make="make"
@@ -311,6 +312,41 @@ 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"
+	echo "Looking for gcc 3.x"
+	found_compat_cc="no"
+	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!"
+	    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 +450,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
 
 ##########################################

  reply	other threads:[~2006-12-19  2:58 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 [this message]
2006-12-19  3:09     ` Paul Brook
2006-12-19  3:23       ` Anthony Liguori

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=45875558.7020501@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.