diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-12-08 15:14:31 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-12-11 21:47:28 +0000 |
commit | 590ef99df74581e6b7595e545c12594012653de8 (patch) | |
tree | 8bf83331dada639d22f21953a67784ca438344a2 /documentation/yocto-project-qs | |
parent | ef888dd58f431866db2472753643f3f848fece21 (diff) | |
download | poky-590ef99df74581e6b7595e545c12594012653de8.tar.gz |
uninative: Handle futex hangs caused by glibc version mismatches
We've been seeing hangs in smart on the autobuilders where it hangs in
pthread futex calls. It appears to happen when some components are
installed from sstate (which use the interpreter from uninative)
and other components are built natively (and use the host's interpreter).
Its primarily affecting software which uses shared memory with futexs in
for locking purposes (which bdb does called from librpm from smart).
This isn't an issue in pyro and rocko and beyond since they use recipe
specific sysroots which included a change to always change to the
uninative interpreter. We could backport those changes but they're
fairly invasive changes to the sstate code. This patch is a more
minimal change which ensures binaries are always using the uninative
interpreter regardless of whether they're built locally or installed
from sstate.
This is only an issue if you're using an sstate mirror and hosts
with a variety of different libc versions. It has only become an issue
on recent libc versions where there was clearly some forwards compatibility
issue introduced.
(From OE-Core rev: 6b149a88cd33c65c7f306f785f4d24ee2909809c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
0 files changed, 0 insertions, 0 deletions