From: Saul Wold <sgw@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pkg-config: allow kernel to be build with esdk
Date: Fri, 23 Jun 2017 16:38:26 -0700 [thread overview]
Message-ID: <1498261106.13914.248.camel@linux.intel.com> (raw)
In-Reply-To: <1498229267.24449.132.camel@linuxfoundation.org>
On Fri, 2017-06-23 at 15:47 +0100, Richard Purdie wrote:
> On Wed, 2017-06-14 at 07:03 -0700, Saul Wold wrote:
> >
> > When the kernel's menuconfig target is called while using the esdk
> > or
> > an esdk-based container, the pkg-config info that is found is not
> > correct.
> > The pkg-config info is for the target, but we need the eSDK's
> > information in order to build the host based menuconfig.
> >
> > The new pkg-config script checks both that it's in SDK and being
> > called from the check-lxdialog script in order to limit the scope
> > of
> > when the pkg-config automagically switches to pkg-config-native.
> >
> > This script also replaces the default pkg-config-native script.
> >
> > [YOCTO #11155]
> >
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
>
> To be honest, I'm scared of adding this kind of complexity to the
> system. I appreciate the problem you're trying to solve but I worry
> adding this kind of change is complex, invasive and introduces too
> much
> risk.
>
> I have some specific worries with this implementation too, in
> particular that it changes on target pkg-config, it really should
> only
> change nativesdk-pkgconfig? If we have risk, we want to minimise that
> risk and adding this wrapper everywhere doesn't seem to do that...
>
There is no nativesdk-pkgconfig, but I had some confusion around the
pkg-config-native and it's usage of a pkg-config binary. I was getting
some recursion initially and my feeble brain thought it was the target
version :-(.
I have rebuilt this patch and will send a V2 that ONLY affects the pkg-
config-native, basically expands the script to check if it's being
called as -native or from the Kernel's check-lxdialog.
I am also going to change the script such that it checks it's base name
of pkg-config and only then add the parent pid name checking.
I hope that will mitigate the risk.
Sau!
> Cheers,
>
> Richard
>
>
prev parent reply other threads:[~2017-06-23 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 14:03 [PATCH] pkg-config: allow kernel to be build with esdk Saul Wold
2017-06-20 14:03 ` Saul Wold
2017-06-23 14:47 ` Richard Purdie
2017-06-23 23:38 ` Saul Wold [this message]
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=1498261106.13914.248.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.