From: Anthony Liguori <aliguori@us.ibm.com>
To: malc <av1474@comtv.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [COMMIT 8a2e6ab] Remove CFLAGS parameter in cc-option
Date: Wed, 09 Sep 2009 19:51:00 -0500 [thread overview]
Message-ID: <4AA84D74.4030905@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909100434590.4541@linmac.oyster.ru>
malc wrote:
> On Thu, 10 Sep 2009, Juan Quintela wrote:
>
>
>> malc <av1474@comtv.ru> wrote:
>>
>>> On Wed, 9 Sep 2009, Anthony Liguori wrote:
>>>
>>>
>>>> From: Juan Quintela <quintela@redhat.com>
>>>>
>>>> With cc-option we are testing if gcc just accept a particular option, we
>>>> don't need CFLAGS at all. And this fixes the recursive problem with
>>>> CFLAGS
>>>>
>>> This is nonsense, previous options, those in CFLAGS, might conflict with
>>> the new ones.
>>>
>> The only thing that we are testing is if gcc support that _option_
>>
>> What is the use case tat you have in mind? A first grep on gcc man page
>> don't show options that conflict with each other.
>>
>
> If you want artificial exmaples i can come up with plenty, and from the
> top of my head -m486 with -msse2 are quite incompatible with each other,
> furthermore, point is this - testing one option in isolation is broken.
>
I think this is a pretty valid point. I think it's worth while to try
and better understand what the recursion problem was in the first place.
--
Regards,
Anthony Liguori
next parent reply other threads:[~2009-09-10 0:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909092236.n89MaDVS020267@d01av01.pok.ibm.com>
[not found] ` <Pine.LNX.4.64.0909100409430.2139@linmac.oyster.ru>
[not found] ` <m3d45z63ry.fsf@neno.mitica>
[not found] ` <Pine.LNX.4.64.0909100434590.4541@linmac.oyster.ru>
2009-09-10 0:51 ` Anthony Liguori [this message]
[not found] ` <m3r5uf4odd.fsf@neno.mitica>
2009-09-10 1:51 ` [Qemu-devel] Re: [COMMIT 8a2e6ab] Remove CFLAGS parameter in cc-option Anthony Liguori
2009-09-11 15:44 ` Thomas Monjalon
2009-09-11 15:52 ` Juan Quintela
2009-09-11 16:06 ` Thomas Monjalon
2009-09-11 16:17 ` Juan Quintela
2009-09-11 16:35 Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2009-09-11 16:40 Thomas Monjalon
2009-09-11 16:53 Thomas Monjalon
2009-09-11 16:54 Thomas Monjalon
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=4AA84D74.4030905@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).