From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH] Allow users to override compiler checks for gcc3 by only using --disable-gcc-check as done in qemu
Date: Mon, 8 Oct 2007 10:29:37 -0500 [thread overview]
Message-ID: <20071008152937.GA2137@tapir> (raw)
Allow users to override the compiler checks for gcc3 that are required for
compatibility with qemu in the same way that qemu does.
If the qemu-cc option is not used but disable-gcc-check is requested then
assume that the default system gcc should be used (chosen by name)
This patch fixes sourceforge bug id 1807620
Signed-off-by: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
---
configure | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index d9292fe..33a56d2 100755
--- a/configure
+++ b/configure
@@ -63,8 +63,12 @@ while [[ "$1" = -* ]]; do
done
if [[ -z "$qemu_cc" ]]; then
- echo "$0: cannot locate gcc 3.x. please install it or specify with --qemu-cc"
- exit 1
+ if [[ -z "$disable_gcc_check" ]]; then
+ echo "$0: cannot locate gcc 3.x. please install it or specify with --qemu-cc"
+ exit 1
+ else
+ qemu_cc=gcc
+ fi
fi
libkvm_kerneldir="$kerneldir"
--
1.5.2.5
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-08 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 15:29 Carlo Marcelo Arenas Belon [this message]
2007-10-08 16:23 ` [PATCH] Allow users to override compiler checks for gcc3 by only using --disable-gcc-check as done in qemu Avi Kivity
[not found] ` <470A5982.5080606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-09 6:02 ` Carlo Marcelo Arenas Belon
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=20071008152937.GA2137@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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