On 4/26/21 11:06 AM, Khem Raj wrote:
> This ensures that if libseccomp is installed on build host then it does
> not resort to use it.
>
> Fixes
> checking for libseccomp... (cached) yes
> checking how to link with libseccomp... /usr/lib/libseccomp.so
Thanks
-armin
>
> Signed-off-by: Khem Raj <raj.k...@gmail.com>
> Cc: Armin Kuster <akuster...@gmail.com>
> ---
> meta/recipes-support/gnutls/gnutls_3.7.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/gnutls/gnutls_3.7.1.bb
> b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
> index 3e1958c969..350d0a018b 100644
> --- a/meta/recipes-support/gnutls/gnutls_3.7.1.bb
> +++ b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
> @@ -31,7 +31,7 @@ PACKAGECONFIG ??= "libidn
> ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)}"
>
> # You must also have CONFIG_SECCOMP enabled in the kernel for
> # seccomp to work.
> -PACKAGECONFIG[seccomp] =
> "ac_cv_libseccomp=yes,ac_cv_libseccomp=no,libseccomp"
> +PACKAGECONFIG[seccomp] =
> "--with-libseccomp-prefix=${STAGING_EXECPREFIXDIR},ac_cv_libseccomp=no,libseccomp"
> PACKAGECONFIG[libidn] = "--with-idn,--without-idn,libidn2"
> PACKAGECONFIG[libtasn1] =
> "--with-included-libtasn1=no,--with-included-libtasn1,libtasn1"
> PACKAGECONFIG[p11-kit] = "--with-p11-kit,--without-p11-kit,p11-kit"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151015):
https://lists.openembedded.org/g/openembedded-core/message/151015
Mute This Topic: https://lists.openembedded.org/mt/82384782/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
