I try to update the following stage3 with a qemu user chroot: http://distfiles.gentoo.org/releases/arm/autobuilds/current-stage3-armv7a_hardfp/stage3-armv7a_hardfp-20141023.tar.bz2 I follow the Gentoo Emebedded Handbook part 1 chapter 5: https://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=5 I built my static qemu binary package with user arm. I configured binfmt_misc with the qemu-wrapper program in the root of the stage3. I installed the binary package in the stage3 and bind mount portage, dev, proc, ... I chrooted in the stage3 and it seems ok. But I can't merge anything because all emerge commend ends during the 'unpack' with this trace: >>> Emerging (1 of 2) dev-lang/python-exec-2.0.1-r1 * python-exec-2.0.1.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] /bin/bash: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior * is known to be triggered by things such as failed variable assignments * (bug #190128) or bad substitution errors (bug #200313). Normally, before * exiting, bash should have displayed an error message above. If bash did * not produce an error message above, it's possible that the ebuild has * called `exit` when it should have called `die` instead. This behavior * may also be triggered by a corrupt bash binary or a hardware problem * such as memory or cpu malfunction. If the problem is not reproducible or * it appears to occur randomly, then it is likely to be triggered by a * hardware problem. If you suspect a hardware problem then you should try * some basic hardware diagnostics such as memtest. Please do not report * this as a bug unless it is consistently reproducible and you are sure * that your bash binary and hardware are functioning properly. ebuild python-exec-2.0.1-r1.ebuild unpack gives the same result. I think the problem comes from the error message on libgcc_s.so.1: /bin/bash: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory I run /bin/bash on my chroot without problem then my guess is it's somehow related to sandbox or some features in portage. I don't know how to debug that, can you give me any hints to dig in the problem ? Reproducible: Always
Created attachment 395658 [details] The emerge --info in the chroot
Created attachment 395660 [details] emerge --info on my host system
Please figure out what is causing the issue. If you find that the solution is of a global nature, then reopen this bug report and propose a correction.
Running 'ldconfig' in the chroot fixes the issue. Maybe a word on the Gentoo Embedded Handbook is needed.
