public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "hongxu" <hongxu.jia@windriver.com>
To: openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org, raj.khem@gmail.com,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Upgrade uninative to fix multiple native build failures in old unprivileged docker
Date: Tue, 31 Aug 2021 09:36:33 +0800	[thread overview]
Message-ID: <f1f1ee17-1f81-8791-b87e-3692a0cafe2a@windriver.com> (raw)
In-Reply-To: <169FF42BF9440142.22970@lists.openembedded.org>

Hi Richard & Michael,

The reason why I submitted patch [glibc: fix create thread failed in old
unprivileged docker] is there are build failures with uninative 3.3 under
old unprivileged docker. If the glibc fix is OK, would you please upgrade
a new uninative that contains the fix.

Here are the steps to reproduce the failures
1) Run a container without privileged
$ docker pull resin/yocto-build-env
$ docker run -it -e HOST_UID="$(id -u)" -e DISTRO="poky" -v $PWD:/mnt -w 
/mnt resin/yocto-build-env bash

2) Poky build preparation
$ apt update && apt install -y liblz4-tool zstd
$ useradd -u $HOST_UID -m -d /mnt/test -s /bin/bash test
$ su test
$ cd ~

3) Setup a Poky project with uninative enabled
$ git clone --branch master --single-branch git://git.yoctoproject.org/poky
$ cd poky && . ./oe-init-build-env
$ echo 'INHERIT += "uninative"' >> conf/local.conf

4) Build failures
...
$ bitbake ninja-native
|ninja: fatal: posix_spawn: Operation not permitted

$ bitbake go-cross-core2-64
|runtime/cgo: pthread_create failed: Operation not permitted

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

After applying the glibc fix, I built a uninative tarball on my local
project to replace uninative 3.3. Then repeat above steps, no above
failures any more

//Hongxu


  parent reply	other threads:[~2021-08-31  1:36 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   ` hongxu [this message]
2021-08-31 17:58     ` [OE-core] Upgrade uninative to fix multiple native build failures " Robert Berger
2021-08-31 18:18       ` 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=f1f1ee17-1f81-8791-b87e-3692a0cafe2a@windriver.com \
    --to=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