From: Mike Frysinger <vapier@gentoo.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: do not quote $PKG_CONFIG
Date: Wed, 18 Jul 2012 08:13:53 -0400 [thread overview]
Message-ID: <201207180813.54820.vapier@gentoo.org> (raw)
In-Reply-To: <50043A3F.5010501@weilnetz.de>
[-- Attachment #1: Type: Text/Plain, Size: 2440 bytes --]
On Monday 16 July 2012 11:58:55 Stefan Weil wrote:
> Am 16.07.2012 17:39, schrieb Eric Blake:
> > On 07/15/2012 01:54 PM, 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.
> >
> > Actually, it IS a good idea. The de facto standard build environment
> > requires that pkg-config is not allowed to live in a path containing
> > spaces, precisely so that you can override the variable to pass options
> > to your preferred location of pkg-config; and if your build setup is
> > truly so messed up as to have pkg-config installed in a canonical
> > location with spaces, then you can also tweak your unusual environment
> > to provide a symlink to pkg-config that does not contain spaces as the
> > workaround.
>
> That sounds reasonable. Then the following patch was at least partially
> unnecessary:
>
> commit 17884d7b6462b0fe497f08fec6091ffbe04caa8d
> Author: Sergei Trofimovich <slyfox@gentoo.org>
> Date: Tue Jan 31 22:03:45 2012 +0300
>
> ./configure: request pkg-config to provide private libs when static
> linking
>
> Added wrapper around pkg-config to allow:
> - safe options injection via ${QEMU_PKG_CONFIG_FLAGS}
> - spaces in path to pkg-config
>
> Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
> CC: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> With Mike's new patch, QEMU_PKG_CONFIG_FLAGS is no longer needed
> because options can be passed using the pkg-config macro.
> I suggest to remove it.
i'm ambivalent on the additional functionality that qemu provides in its build
system -- i'm just concerned with the baseline being the same as all other
build systems. some people probably find this handy.
-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-18 12:13 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
2012-07-16 15:39 ` Eric Blake
2012-07-16 15:58 ` Stefan Weil
2012-07-18 12:13 ` Mike Frysinger [this message]
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=201207180813.54820.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=eblake@redhat.com \
--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).