new ARM profile and new CHOST

[potuz]

The new 17.0 profile is encouraged for arm. This involves a change in CHOST. In my particular case of a raspberry-pi this would change from

armv7a-hardfloat-linux-gnueabi

to

armv7a-unknown-linux-gnueabihf

I am supposed to use the script in
https://dev.gentoo.org/~chewi/armhf-migrate.bash

And I trust the Gentoo devs have done as always a fantastic job at checking many use cases.

I do have however a couple of questions.

1) I use distcc to crosscompile on this arm machine, will this script rebuild the system on my distcc server or natively on ARM?

2) What should I do on the distcc server? Should I install a new target for crossdev?

At first I was leaning towards not changing the profile, but the problem is that when those things get deprecated it's really hard to update.

[NeddySeagoon]

potuz,

This script runs on the ARM system. It does nothing for the distcc helper(s).

You need to run

Code: Select all

crossdev -t <new_target>

there.

Moved to Gentoo on ARM, as it fits better there.

[potuz]

potuz,

This script runs on the ARM system. It does nothing for the distcc helper(s).

You need to run

Code: Select all

crossdev -t <new_target>

there.

Moved to Gentoo on ARM, as it fits better there.

Thanks, would it help if I build the toolchain on the helper before running the script? would then the script rebuild some of the components using distcc?

[NeddySeagoon]

potuz,

You can't use distcc with gcc and I've seen in make a mess of glibc too.

In theory, you can cross compile all the bits then install the binaries.
The script does a lot more than that though.