qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -cc checking wrong
Date: Sun, 7 May 2006 21:13:58 -0400	[thread overview]
Message-ID: <20060508011358.GA23381@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200605080153.03721.paul@codesourcery.com>

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

On Mon, May 08, 2006 at 01:53:03AM +0100, Paul Brook wrote:
> You really should test your patches. The patch you attached generates an error 
> if the compiler works.
> 
> Paul
> 

Whoops, sorry about that. I only tested the --cc="ccache gcc" case.

Here's the correct patch.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

[-- Attachment #2: configure.patch --]
[-- Type: text/plain, Size: 452 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
 

      reply	other threads:[~2006-05-08  1:14 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
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 [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=20060508011358.GA23381@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 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).