Talk:Cross build environment

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 10:44, 5 November 2024 (UTC)
:: Your reply ~~~~

New environment questions

Talk status

This discussion is done as of 2023-09-07.

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. — The preceding unsigned comment was added by MJaoune (talk • contribs)

Script was removed a long time ago so closing

Immolo (talk) 08:55, 7 September 2023 (UTC)

Several issues

Talk status

This discussion is done as of 2023-09-07.

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)

Reading though I'm not quite sure why you think there are issues but maybe they were fixed. You might find Embedded_Handbook/General/Compiling_with_qemu_user_chroot better if someone is having issues though and I'll add it as a See also now.

Immolo (talk) 08:59, 7 September 2023 (UTC)

Rpi4 and Kernel config

Talk status

This discussion is done as of 2023-09-07.

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)

Please be confident and make the change if you know it is needed.

Immolo (talk) 09:01, 7 September 2023 (UTC)