Talk:Cross build environment

New environment questions
For emerge-chroot: The new environment has no Portage, how will "portageq" and "emerge" work in the first place?

In the chroot script: How will the user be able to execute mount, binaries at /usr/local/bin are only accessible to users and not root.

Several issues
Adding to the above, there are many issues here:
 * It is not clear what has to be run on the main environment and what has to be run in the choot.
 * Outdated system locations: /var/db/repos/gentoo is no more
 * crossdev deploys a chroot with busybox. Unfortunately, there is an issue with /bin/sh (which is indeed a "busybox sh") inside the chroot: for some reason, $PATH is ignored thus qemu-user is unable to spawn the required command. Instead you will get the message "qemu: no user program specified" when running configure scripts and of course nothing is run which badly breaks things. See the bug report here => https://bugs.busybox.net/show_bug.cgi?id=13746
 * The issue with namespaces and QEMU is related to this upstream bug => https://bugs.launchpad.net/qemu/+bug/1829459

Admnd (talk) 21:30, 11 April 2021 (UTC)

Rpi4 and Kernel config
Crossdev will fail to emerge 'aarch64-unknown-linux-gnu' if you have 'CONFIG_COMPAT_BRK=n' (disabled) in your kernel. To fix this, set the option to Y (enabled) and recompile.

Mazzog (talk) 10:34, 24 July 2022 (UTC)