From: justin <jlec@gentoo.org>
To: Silvio Fricke <silvio.fricke@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [RFC] [PATCH] pkg-config default search pathes
Date: Mon, 11 Aug 2014 19:23:19 +0200 [thread overview]
Message-ID: <53E8FC07.1090609@gentoo.org> (raw)
In-Reply-To: <cover.1407766447.git.silvio.fricke@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On 11/08/14 16:22, Silvio Fricke wrote:
> Hi,
>
> please review this patch.
> I'm a little bit unsure if this patch is technicaly state-of-the-art because
> kbuild does it right. The problem is that some cross-toolchains (on my box is
> yocto installed) change the pkg-config search pathes to do some package-config
> setups for cross compiling.
> But the init of the toolchain manipulates PKG_CONFIG_SYSROOT_DIR and
> PKG_CONFIG_PATH variables that a pkg-config call searches in the wrong place to
> find the package and gives back the wrong values which we use to test the
> availability of ncurses installation and this break the [x,g,menu]config.
>
> Some recommendations for this?
>
>
Hi Silvio,
What would happen in a real crosscompile case?
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
next prev parent reply other threads:[~2014-08-11 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 14:22 [RFC] [PATCH] pkg-config default search pathes Silvio Fricke
2014-08-11 14:22 ` [RFC] [PATCH] kconfig: menuconfig: pkg-config should base upon default configuration Silvio Fricke
2014-08-22 11:07 ` Michal Marek
2014-08-11 17:23 ` justin [this message]
2014-08-11 17:41 ` [RFC] [PATCH] pkg-config default search pathes Silvio Fricke
2014-08-11 18:04 ` justin
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=53E8FC07.1090609@gentoo.org \
--to=jlec@gentoo.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=silvio.fricke@gmail.com \
--cc=yann.morin.1998@free.fr \
/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).