All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Armin Kuster" <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gnutls: Point to staging area for finding seccomp libs and includes
Date: Mon, 26 Apr 2021 11:19:19 -0700	[thread overview]
Message-ID: <efaec314-294b-8689-a777-d8d363f72174@gmail.com> (raw)
In-Reply-To: <20210426180615.2837459-1-raj.khem@gmail.com>



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.khem@gmail.com>
> Cc: Armin Kuster <akuster808@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"


      reply	other threads:[~2021-04-26 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:06 [PATCH] gnutls: Point to staging area for finding seccomp libs and includes Khem Raj
2021-04-26 18:19 ` Armin Kuster [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=efaec314-294b-8689-a777-d8d363f72174@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.