From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Improve gcc 3 checking
Date: Mon, 18 Dec 2006 20:25:05 -0600 [thread overview]
Message-ID: <45874D81.1090508@cs.utexas.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
In Xen, we use a single top level Makefile to build everything. This
means we automatically kick off the configure script. It would be nice
if QEMU's configure did a better job of finding existing GCC 3.x
installs so that the user didn't have to manually specific the location.
The attached patch adds a white list to configure to check for various
versions of GCC 3.x. The white list so far covers the various versions
of GCC in recent versions of OpenSUSE, Fedora, RHEL, and Ubuntu
(presumably also Debian).
I don't think this patch will impact any of the other platforms but
getting some testing first on weird platforms (Solaris and Win32
especially) would be helpful.
Regards,
Anthony Liguori
[-- Attachment #2: qemu-gcc-3x.diff --]
[-- Type: text/x-patch, Size: 2029 bytes --]
diff -r ca36b7b88df2 configure
--- a/configure Mon Dec 18 18:57:19 2006 -0600
+++ b/configure Mon Dec 18 20:18:01 2006 -0600
@@ -22,6 +22,7 @@ static="no"
static="no"
cross_prefix=""
cc="gcc"
+gcc3_list="gcc32 gcc33 gcc34 gcc-3.2 gcc-3.3 gcc-3.4"
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 check_cc "$cc" ; 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
##########################################
next reply other threads:[~2006-12-19 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 2:25 Anthony Liguori [this message]
2006-12-19 2:31 ` [Qemu-devel] [PATCH] Improve gcc 3 checking Paul Brook
2006-12-19 2:58 ` Anthony Liguori
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=45874D81.1090508@cs.utexas.edu \
--to=aliguori@cs.utexas.edu \
--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).