All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
	<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Allow users to override compiler checks for gcc3 by only using --disable-gcc-check as done in qemu
Date: Mon, 08 Oct 2007 18:23:30 +0200	[thread overview]
Message-ID: <470A5982.5080606@qumranet.com> (raw)
In-Reply-To: <20071008152937.GA2137@tapir>

Carlo Marcelo Arenas Belon wrote:
> Allow users to override the compiler checks for gcc3 that are required for
> compatibility with qemu in the same way that qemu does.
>
> If the qemu-cc option is not used but disable-gcc-check is requested then
> assume that the default system gcc should be used (chosen by name)
>
> This patch fixes sourceforge bug id 1807620
>
>   

This deviates from normal qemu, no?  I think qemu-s --disable-gcc-check
doesn't imply anything about the compiler.



-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  reply	other threads:[~2007-10-08 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 15:29 [PATCH] Allow users to override compiler checks for gcc3 by only using --disable-gcc-check as done in qemu Carlo Marcelo Arenas Belon
2007-10-08 16:23 ` Avi Kivity [this message]
     [not found]   ` <470A5982.5080606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-09  6:02     ` Carlo Marcelo Arenas Belon

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=470A5982.5080606@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.