From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@cs.utexas.edu>
Subject: Re: [Qemu-devel] [PATCH] Improve gcc 3 checking
Date: Tue, 19 Dec 2006 02:31:06 +0000 [thread overview]
Message-ID: <200612190231.08331.paul@codesourcery.com> (raw)
In-Reply-To: <45874D81.1090508@cs.utexas.edu>
On Tuesday 19 December 2006 02:25, Anthony Liguori wrote:
> +gcc3_list="gcc32 gcc33 gcc34 gcc-3.2 gcc-3.3 gcc-3.4"
Shouldn't we be preferring newer compilers?
> + echo "Looking for gcc 3.x"
We shouldn't do this if if the user explicitly specified a compiler.
Replacing explicit user setting with guesses is bad.
Paul
next prev parent reply other threads:[~2006-12-19 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 2:25 [Qemu-devel] [PATCH] Improve gcc 3 checking Anthony Liguori
2006-12-19 2:31 ` Paul Brook [this message]
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=200612190231.08331.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=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).