From: Brad Smith <brad@comstyle.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Andreas F??rber <andreas.faerber@web.de>,
patches@linaro.org, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: Default to 'cc', not 'gcc', on MacOS X
Date: Thu, 22 Nov 2012 03:45:04 -0500 [thread overview]
Message-ID: <20121122084504.GD4013@rox.home.comstyle.com> (raw)
In-Reply-To: <CAFEAcA81T-qKXh241Aaz3=mZWWQg+ZmuFK1kzCOrKg1bc5STQA@mail.gmail.com>
On Thu, Nov 22, 2012 at 08:41:19AM +0000, Peter Maydell wrote:
> On 22 November 2012 08:38, Brad Smith <brad@comstyle.com> wrote:
> > On Thu, Nov 22, 2012 at 08:33:17AM +0000, Peter Maydell wrote:
> >> On 22 November 2012 00:04, Andreas F??rber <andreas.faerber@web.de> wrote:
> >> > But then again there's the question of why not doing it on Linux as well
> >> > now that we seem to compile under clang, we have cc -> gcc-4.7 on
> >> > openSUSE 12.2. Among our supported platforms only Solaris comes to my
> >> > mind where cc might be an incompatible proprietary compiler.
> >>
> >> Do any of the BSDs ship with some odd non-GPL thing as cc ?
> >
> > non-GPL yes, odd no.
>
> Does QEMU build OK with them? Should we be preferring them
> to gcc?
The release notes for 1.3 seem to indicate Clang is supported
now so I would think so. AFAIK FreeBSD -current does not
ship with gcc anymore. Bitrig is a fork of OpenBSD that only
ships with Clang.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2012-11-22 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 16:37 [Qemu-devel] [PATCH] configure: Default to 'cc', not 'gcc', on MacOS X Peter Maydell
2012-11-17 13:02 ` Andreas Färber
2012-11-17 13:10 ` Peter Maydell
2012-11-21 23:19 ` Peter Maydell
2012-11-22 0:04 ` Andreas Färber
2012-11-22 8:33 ` Peter Maydell
2012-11-22 8:38 ` Brad Smith
2012-11-22 8:41 ` Peter Maydell
2012-11-22 8:45 ` Brad Smith [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=20121122084504.GD4013@rox.home.comstyle.com \
--to=brad@comstyle.com \
--cc=aliguori@us.ibm.com \
--cc=andreas.faerber@web.de \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).