On 6/19/19 6:56 AM, Richard Purdie wrote:
> This avoids sstate/uninative relocation issues where a binary was built
> against
> a system with libcrypt.so.1 or libcrypt.so.2 and then run on the opposite by
> ensuring both libraries are in uninative.
Does this affect stable branches?
- armin
> Signed-off-by: Richard Purdie <[email protected]>
> ---
> meta/recipes-core/meta/uninative-tarball.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/meta/uninative-tarball.bb
> b/meta/recipes-core/meta/uninative-tarball.bb
> index 25635fc2f50..39638eb8c55 100644
> --- a/meta/recipes-core/meta/uninative-tarball.bb
> +++ b/meta/recipes-core/meta/uninative-tarball.bb
> @@ -16,6 +16,7 @@ TOOLCHAIN_HOST_TASK = "\
> nativesdk-glibc-gconv-libjis \
> nativesdk-patchelf \
> nativesdk-libxcrypt \
> + nativesdk-libxcrypt-compat \
> nativesdk-libnss-nis \
> "
>
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
