From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -cc checking wrong
Date: Sun, 7 May 2006 20:18:55 -0400 [thread overview]
Message-ID: <20060508001855.GA15033@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <87d5eppicn.fsf@Janik.cz>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Mon, May 08, 2006 at 12:46:24AM +0200, Pavel Jan?k wrote:
> configure contains:
>
> if [ ! -x "`which $cc`" ] ; then
> echo "Compiler $cc could not be found"
> exit
> fi
>
> You should check if the command compiles, not if it exists and is executable.
Patch attached. Simply tries to compile a dummy program.
> Two wrongs do not make a right.
> -- Linus Torvalds in linux-kernel
I find that quote very ironic ... ;)
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
[-- Attachment #2: configure.patch --]
[-- Type: text/plain, Size: 450 bytes --]
--- configure.orig Sun May 7 20:14:23 2006
+++ configure Sun May 7 20:16:58 2006
@@ -293,8 +293,14 @@
ar="${cross_prefix}${ar}"
strip="${cross_prefix}${strip}"
-if [ ! -x "`which $cc`" ] ; then
- echo "Compiler $cc could not be found"
+# check that gcc is able to compile
+cat > $TMPC <<EOF
+int main(void) {
+}
+EOF
+
+if $cc -o $TMPE $TMPC 2>/dev/null ; then
+ echo "Compiler $cc either does not exist or does not work"
exit
fi
next prev parent reply other threads:[~2006-05-08 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 7:41 [Qemu-devel] -cc checking wrong Pavel Janík
2006-05-07 22:46 ` Pavel Janík
2006-05-08 0:18 ` Jim C. Brown [this message]
2006-05-08 0:34 ` Jim C. Brown
2006-05-08 7:52 ` Pavel Janík
2006-05-08 15:12 ` Jim C. Brown
2006-05-08 18:53 ` Pavel Janík
2006-05-08 19:08 ` Jim C. Brown
2006-05-08 0:53 ` Paul Brook
2006-05-08 1:13 ` Jim C. Brown
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=20060508001855.GA15033@jbrown.mylinuxbox.org \
--to=jma5@umd.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 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.