From: Bernhard Fischer <rep.nop@aon.at>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu Makefile configure
Date: Wed, 3 Jan 2007 17:58:23 +0100 [thread overview]
Message-ID: <20070103165823.GB16663@aon.at> (raw)
In-Reply-To: <20070103161653.GF5849@networkno.de>
On Wed, Jan 03, 2007 at 04:16:53PM +0000, Thiemo Seufer wrote:
>Fabrice Bellard wrote:
>> IMHO, CFLAGS and LDFLAGS overriding should not be allowed for QEMU as it
>> is almost sure to break the dyngen stuff. If ever it is allowed, it
>> should be done so that the CFLAGS for the files used by dyngen are not
>> modified.
>
>That's why I made OP_CFLAGS a separate set of flags.
>
>I append the next version of the patch, which incorporates the
>suggestions made by Daniel and Bernhard, and fixes a gcc3 detection
>bug I introduced earlier.
Is the override directive a common extension?
http://www.opengroup.org/onlinepubs/009695399/utilities/make.html
I'd avoid override if possible and use a different variable instead
(CC_CFLAGS, or the like) to be passed to the .c.o rules
next prev parent reply other threads:[~2007-01-03 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 21:31 [Qemu-devel] qemu Makefile configure Thiemo Seufer
2007-01-03 13:59 ` Thiemo Seufer
2007-01-03 14:23 ` Bernhard Fischer
2007-01-03 15:09 ` Thiemo Seufer
2007-01-07 21:58 ` Pierre d'Herbemont
2007-01-03 14:42 ` Thiemo Seufer
2007-01-03 14:55 ` Daniel Jacobowitz
2007-01-03 15:36 ` Thiemo Seufer
2007-01-03 15:43 ` Fabrice Bellard
2007-01-03 16:16 ` Thiemo Seufer
2007-01-03 16:58 ` Bernhard Fischer [this message]
2007-01-04 12:26 ` Thiemo Seufer
2007-01-05 1:03 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2007-12-09 5:10 Thiemo Seufer
2007-09-22 16:49 Paul Brook
2006-04-23 17:57 Paul Brook
2006-04-30 15:04 ` Leonardo E. Reiter
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=20070103165823.GB16663@aon.at \
--to=rep.nop@aon.at \
--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).