Il 01/05/24 19:54, ralfconn ha scritto:
Il 01/05/24 19:05, Michael ha scritto:
I've built the cross toolchain with 'crossdev --taget
aarch64-unknown-linux-gnu' per wiki [2]. I've selected a 23.0-split-usr
profile on the Pi since this is the one supported by the crossdev
(or so
I understood from the error message when I tried with the non-split-usr
profile on the desktop).
Did you download the correct stage3? There are split-usr and
merged-usr tar
archives. Since split-usr is or will be soon deprecated you better
start with
merged-usr.
I wasn't clear: when I tried to select the merged-usr profile on the
host and on the target I got an error invoking
emerge-aarch64-unknown-linux-gnu on the _host_ telling me that the
profile was 'merged-usr' but the directory layout wasn't. So the
problem is in the directory layout created by crossdev on the host.The
host has a merged-usr profile, I believe the problem is in crossdev
itself. I tried to manually copy files in the crossdev environment to
recreate the merged-usr layout but then the error on the host was even
worse (I forgot what it was) so I went back to split.
Update: stage3 on the pi is merge-usr so the above is bound to fail
sooner or later (as I discovered trying to emerge
app-misc/resolve-march-native on the pi). But, the sys-apps/merge-usr
script accepts a --root parameter, so it is possible to issue, on the host:
# merge-usr --root /usr/aarch64-unknown-linux-gnu
# PORTAGE_CONFIGROOT=/usr/aarch64-unknown-linux-gnu eselect profile set
default/linux/arm64/23.0
and have on the host the same directory layout and profile of the ARM
stage3 installed on the pi.
raffaele
