From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] configure: Append extra cflags and ldflags
Date: Tue, 16 Jun 2009 17:25:58 +0200 [thread overview]
Message-ID: <4A37B986.3040501@web.de> (raw)
In-Reply-To: <f43fc5580906160818g5b2a835fg72cfb52dde6b27fa@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Blue Swirl wrote:
> On 6/15/09, Jan Kiszka <jan.kiszka@web.de> wrote:
>> In order to allow overriding flags that are set by configure, we have to
>> append them instead of prepending as it is done so far.
>
> The help message from configure does not mention about overriding but
> adding flags. Which one is this?
I didn't derive this from the help, but from common practice when using
EXTRA_* flags and the fact the gcc switches that come last override what
comes first. Without the patch, adding your personal -W* switches to the
build is impossible when they collide with some set by configure.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-16 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:09 [Qemu-devel] [PATCH] configure: Append extra cflags and ldflags Jan Kiszka
2009-06-16 15:18 ` [Qemu-devel] " Blue Swirl
2009-06-16 15:25 ` Jan Kiszka [this message]
2009-06-16 17:11 ` [Qemu-devel] " Avi Kivity
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=4A37B986.3040501@web.de \
--to=jan.kiszka@web.de \
--cc=blauwirbel@gmail.com \
--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).