From: Mike Frysinger <vapier@gentoo.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: do not quote $PKG_CONFIG
Date: Sun, 15 Jul 2012 17:53:42 -0400 [thread overview]
Message-ID: <201207151753.43186.vapier@gentoo.org> (raw)
In-Reply-To: <5003200B.4070400@weilnetz.de>
[-- Attachment #1: Type: Text/Plain, Size: 954 bytes --]
On Sunday 15 July 2012 15:54:51 Stefan Weil wrote:
> Am 15.07.2012 22:26, schrieb Mike Frysinger:
> > We should not quote the PKG_CONFIG setting as this deviates from the
> > canonical upstream behavior that gets integrated with all other build
> > systems, and deviates from how we treat all other toolchain variables
> > that we get from the environment.
> >
> > Ultimately, the point is that it breaks passing custom flags directly
> > to pkg-config via the env var where this normally works elsewhere,
> > and it used to work in the past.
>
> What about passing custom flags with QEMU_PKG_CONFIG_FLAGS?
>
> Removing the quotes will not allow paths containing spaces,
> so that's not a good idea.
except that doesn't work with other build variables (like CC/etc...), nor does
it work with the standard pkg-config build environments. making qemu deviate
from the standard to support non-existent setups makes no sense.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-15 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 20:26 [Qemu-devel] [PATCH] configure: do not quote $PKG_CONFIG Mike Frysinger
2012-07-15 19:54 ` Stefan Weil
2012-07-15 21:53 ` Mike Frysinger [this message]
2012-07-16 15:39 ` Eric Blake
2012-07-16 15:58 ` Stefan Weil
2012-07-18 12:13 ` Mike Frysinger
2012-09-16 19:52 ` Mike Frysinger
2012-09-16 20:21 ` Stefan Weil
2012-09-17 5:24 ` Sergei Trofimovich
2012-09-17 19:38 ` Anthony Liguori
2012-09-17 19:51 ` Eric Blake
2013-06-17 6:20 ` [Qemu-devel] [PATCH v2] " Mike Frysinger
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=201207151753.43186.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).