All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] libcap-ng: undefined reference to `pthread_atfork'
Date: Fri, 25 Oct 2019 16:20:08 -0400	[thread overview]
Message-ID: <20191025202008.23715-1-twoerner@gmail.com> (raw)

Some hosts need -lpthread in order to link properly (e.g. openSUSE 15.1).

Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 meta/recipes-support/libcap-ng/libcap-ng_0.7.10.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/libcap-ng/libcap-ng_0.7.10.bb b/meta/recipes-support/libcap-ng/libcap-ng_0.7.10.bb
index 6e6de45494..01ea9a1490 100644
--- a/meta/recipes-support/libcap-ng/libcap-ng_0.7.10.bb
+++ b/meta/recipes-support/libcap-ng/libcap-ng_0.7.10.bb
@@ -3,6 +3,7 @@ require libcap-ng.inc
 inherit lib_package autotools
 
 EXTRA_OECONF += "--without-python --without-python3"
+LDFLAGS_append_class-native = " -lpthread"
 
 BBCLASSEXTEND = "native nativesdk"
 
-- 
2.23.0.37.g745f681289



             reply	other threads:[~2019-10-25 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 20:20 Trevor Woerner [this message]
2019-10-26  9:03 ` [PATCH] libcap-ng: undefined reference to `pthread_atfork' Khem Raj
2019-10-28  3:16   ` Trevor Woerner

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=20191025202008.23715-1-twoerner@gmail.com \
    --to=twoerner@gmail.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.