From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "André Draszik" <git@andred.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] sstate: allow specifying indirect dependencies to exclude from sysroot
Date: Sun, 17 Jun 2018 14:13:01 +0100 [thread overview]
Message-ID: <230ed53b0a05b5ed680ceff2d2004a2ddaa5b351.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180522122553.29109-1-git@andred.net>
On Tue, 2018-05-22 at 13:25 +0100, André Draszik wrote:
> From: André Draszik <andre.draszik@jci.com>
>
> Currently, a dependency on any -native recipe will pull in
> all dependencies of that -native recipe in the recipe
> sysroot. This behaviour might not always be wanted, e.g.
> when that -native recipe depends on build-tools that are
> not relevant for the current recipe.
>
> This change adds a SSTATE_EXCLUDEDEPS_SYSROOT variable,
> which will be evaluated for such recursive dependencies to
> be excluded. The idea is similar to
> http://lists.openembedded.org/pipermail/openembedded-core/2018-Jan
> uary/146324.html
> except that the list is not hard-coded anymore.
>
> SSTATE_EXCLUDEDEPS_SYSROOT is evaluated as two regular
> expressions of recipe and dependency to ignore, e.g. in
> the above flex-native / bison-native use-case, one would
> specify
>
> SSTATE_EXCLUDEDEPS_SYSROOT = ".*->(flex|bison)-native"
>
> in layer.conf.
>
> The existing special handling of "-initial" as well as
> "base-passwd" and "shadow-sysroot" could also be
> streamlined:
>
> SSTATE_EXCLUDEDEPS_SYSROOT += "\
> .*->.*-initial.* \
> .*(base-passwd|shadow-sysroot)->.* \
> "
>
> Another anticipated user is meta-java, where certain newer
> JDKs can only be bootstrapped (built) using older JDKs,
> but it doesn't make much sense to copy all those older
> JDKs and their own build tools (ant, etc.) into the
> sysroot of recipes wanting to be built using the newer JDK
> (only), e.g.:
>
> SSTATE_EXCLUDEDEPS_SYSROOT += "\
> openjdk-8-native->(ant-native|attr-native|coreutils-
> native|icedtea7-native|libxslt-native|make-native|openssl-native|zip-
> native|unzip-native) \
> "
>
> Signed-off-by: André Draszik <andre.draszik@jci.com>
> ---
> meta/classes/sstate.bbclass | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
I have some reservations about this series as I've previously mentioned
but I had a try at testing it on the autobuilder:
https://autobuilder.yocto.io/builders/build-appliance/builds/1059/steps/BuildImages_1/logs/stdio
Basically binutils-cross is bust with errors like:
| x86_64-poky-linux-ar: error while loading shared libraries: libfl.so.2: cannot open shared object file: No such file or directory
| make[5]: *** [libaudio_resampler_sse.la] Error 127
There are a ton of other failures, I've not waded through them but I'm
guessing there are similar issues.
Cheers,
Richard
next prev parent reply other threads:[~2018-06-17 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 12:25 [PATCH 1/4] sstate: allow specifying indirect dependencies to exclude from sysroot André Draszik
2018-05-22 12:25 ` [PATCH 2/4] sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping *-initial recipes André Draszik
2018-05-22 12:25 ` [PATCH 3/4] sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping base-passwd|shadow-sysroot recipes André Draszik
2018-05-22 12:25 ` [PATCH 4/4] sstate: avoid indirect bison/flex-native dependencies (via SSTATE_EXCLUDEDEPS_SYSROOT) André Draszik
2018-05-22 12:33 ` Richard Purdie
2018-05-22 12:44 ` André Draszik
2018-05-22 12:36 ` [PATCH 1/4] sstate: allow specifying indirect dependencies to exclude from sysroot Richard Purdie
2018-05-22 12:48 ` André Draszik
2018-05-22 12:51 ` Richard Purdie
2018-05-23 15:49 ` André Draszik
2018-06-17 13:13 ` Richard Purdie [this message]
2018-08-09 9:00 ` André Draszik
2018-08-09 9:26 ` Richard Purdie
2018-08-15 13:40 ` Richard Purdie
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=230ed53b0a05b5ed680ceff2d2004a2ddaa5b351.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=git@andred.net \
--cc=openembedded-core@lists.openembedded.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