It seems that when installing glibc from a binpkg, when it gets to the locale-gen stage, the following line: locale-gen ${inplace} --jobs $(makeopts_jobs) ... Is using makeopts_jobs from the host. So I build packages on a machine with -j8, but this target is a Rev1 Raspberry Pi with 256MB of RAM and it cannot handle this. Reproducible: Always
I think I successfully worked around it as follows: - Use qtbz2 -s to split the package into tarball and xpak - Use qxpak -x to unpack the xpak - Uncompress environment.bz2, edit the offending -j8, then recompress - qxpak -c to recreate the xpak - qtbx2 -j to re-join the tarball and xpak into tbz2 - Then ran emaint binhost to regenerate the package metadata
Looks similar to bug #680782. Which USE-flags you are using for glibc? USE=compile-locales is one option to avoid it.
Default USE for arm, which is currently: crypt multiarch ssp static-libs -audit -caps -cet -compile-locales -custom-cflags -doc -gd -headers-only -multilib -nscd -profile -selinux -static-pie -suid -systemtap -test -vanilla I wasn't aware of compile-locales, but wouldn't that bloat the tbz2 if it includes all locales, which I'm just going to regenerate post install? I guess I could filter using INSTALL_MASK, but then I'd have to remember to rebuild or I have 0 locales; that's also kinda hacky. The aforementioned bug seems to state in the last comment this was fixed in 2.29-r5. Was this fix reverted?
I don't think anything was fixed in linked bug. The only change was to introduce USE=compile-locales.
