All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: Qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ./configure --help and gcc checks
Date: Thu, 6 Apr 2006 15:40:53 -0400	[thread overview]
Message-ID: <20060406194053.GA7339@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20060406123330.44792.qmail@web26804.mail.ukl.yahoo.com>

having configure check for gcc3, gcc31, gcc32, gcc33, gcc34, etc before checking
for gcc itself might work.

is it really worth the trouble to check every possible combination?

On Thu, Apr 06, 2006 at 02:33:30PM +0200, Sylvain Petreolle wrote:
> Hi people,
> I have gcc 3.2.3 (run as gcc32) and gcc 4.1.0.
> 
> ./configure --help runs the gcc check, thus displaying the following error :
> ERROR: "gcc" looks like gcc 4.x
> 
> IMHO this should be changed to avoid running things like this :
> ./configure --cc=gcc32 --help
> 
> Do agree with that ?
> 
> Kind regards,
> Sylvain Petreolle (aka Usurp)
> --- --- --- --- --- --- --- --- --- --- --- --- ---
> Listen to free Music: www.jamendo.com
> 
> Tired of a proprietary Windows on your computer ?
> Use free ReactOS instead ( http://www.reactos.org )
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

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

  reply	other threads:[~2006-04-06 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 12:33 [Qemu-devel] ./configure --help and gcc checks Sylvain Petreolle
2006-04-06 19:40 ` Jim C. Brown [this message]
2006-04-06 20:31   ` Kevin F. Quinn
2006-04-06 20:36     ` Sylvain Petreolle
2006-04-06 20:40   ` Sylvain Petreolle
2006-04-06 21:30     ` Jim C. Brown
2006-04-06 22:59 ` Kevin F. Quinn

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=20060406194053.GA7339@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.