public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Robert Berger" <oecore.mailinglist@gmail.com>
To: hongxu <hongxu.jia@windriver.com>,
	openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org, raj.khem@gmail.com,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Upgrade uninative to fix multiple native build failures in old unprivileged docker
Date: Tue, 31 Aug 2021 20:58:37 +0300	[thread overview]
Message-ID: <5dee0c30-b658-b730-44ee-a9c2159d21e7@gmail.com> (raw)
In-Reply-To: <f1f1ee17-1f81-8791-b87e-3692a0cafe2a@windriver.com>

Hi,

I just experienced this problem in Docker version 19.03.13, build 4484c46d9d

 > $ bitbake pkgconfig-native
 > | configure: error: I can't find the libraries for the thread
 > implementation
 > ...

Can you please tell me what patches I need to apply to get this to work?

How will this be handled upstream?

I guess people would want to run a build in an unprivileged container.

Regards,

Robert

  reply	other threads:[~2021-08-31 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169FF34664D4ACC1.22970@lists.openembedded.org>
2021-08-30  2:20 ` [PATCH V3] glibc: fix create thread failed in old unprivileged docker hongxu
2021-08-31 20:11   ` Richard Purdie
2021-09-01  0:22     ` hongxu
     [not found] ` <169FF42BF9440142.22970@lists.openembedded.org>
2021-08-31  1:36   ` Upgrade uninative to fix multiple native build failures " hongxu
2021-08-31 17:58     ` Robert Berger [this message]
2021-08-31 18:18       ` [OE-core] " Martin Jansa
2021-08-31 19:50       ` Richard Purdie

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=5dee0c30-b658-b730-44ee-a9c2159d21e7@gmail.com \
    --to=oecore.mailinglist@gmail.com \
    --cc=hongxu.jia@windriver.com \
    --cc=mhalstead@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox