From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jeremy Puhlman <jpuhlman@mvista.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [kirkstone][PATCH] gcc: depend on zstd-native
Date: Wed, 01 Jun 2022 23:15:10 +0100 [thread overview]
Message-ID: <17046dccfb415c1afa9851ab45b90fe04114798a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220601205504.3464879-1-jpuhlman@mvista.com>
On Wed, 2022-06-01 at 16:55 -0400, Jeremy Puhlman wrote:
> Sharing sstate cache binaries between two systems, one with libzstd installed
> and the other without, leads to various gcc components being linked against
> the system libzstd and failing to run on the system with out it installed.
>
> Make zstd-native from our system available.
>
> Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com>
> ---
> meta/recipes-devtools/gcc/gcc-11.2.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc b/meta/recipes-devtools/gcc/gcc-11.2.inc
> index 68e0d203fc..e2a28468f5 100644
> --- a/meta/recipes-devtools/gcc/gcc-11.2.inc
> +++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
> @@ -11,7 +11,7 @@ BINV = "11.2.0"
> FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
>
> DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
> -NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
> +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native zstd-native"
>
> LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"
Does master have that issue?
Cheers,
Richard
next prev parent reply other threads:[~2022-06-01 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:55 [kirkstone][PATCH] gcc: depend on zstd-native Jeremy A. Puhlman
2022-06-01 22:15 ` Richard Purdie [this message]
2022-06-01 22:27 ` [OE-core] " Jeremy Puhlman
2022-06-01 22:29 ` Steve Sakoman
2022-06-01 23:04 ` Jeremy Puhlman
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=17046dccfb415c1afa9851ab45b90fe04114798a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jpuhlman@mvista.com \
--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 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.