From: "Martin Jansa" <Martin.Jansa@gmail.com>
To: Robert Berger <oecore.mailinglist@gmail.com>
Cc: hongxu <hongxu.jia@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <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:18:18 +0200 [thread overview]
Message-ID: <CA+chaQehkDRb1PDX9nVq_XCYiqEw2vb-a2T0vNBri3x_T82zdQ@mail.gmail.com> (raw)
In-Reply-To: <5dee0c30-b658-b730-44ee-a9c2159d21e7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Tue, Aug 31, 2021 at 7:58 PM Robert Berger <oecore.mailinglist@gmail.com>
wrote:
> 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?
>
https://lists.openembedded.org/g/openembedded-core/message/155465
and rebuild new uninative tarball with this applied.
> How will this be handled upstream?
>
Hopefully v20.10.9 docker will be released soon with:
https://github.com/moby/moby/commit/9f6b562dd12ef7b1f9e2f8e6f2ab6477790a6594
[-- Attachment #2: Type: text/html, Size: 1390 bytes --]
next prev parent reply other threads:[~2021-08-31 18:18 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 ` [OE-core] " Robert Berger
2021-08-31 18:18 ` Martin Jansa [this message]
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=CA+chaQehkDRb1PDX9nVq_XCYiqEw2vb-a2T0vNBri3x_T82zdQ@mail.gmail.com \
--to=martin.jansa@gmail.com \
--cc=hongxu.jia@windriver.com \
--cc=mhalstead@linuxfoundation.org \
--cc=oecore.mailinglist@gmail.com \
--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 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.