crossdev build chain

[axl]

Interesting. You may have your reasons to have that third linux in /mnt/blanc/rootfs/pi.

I only need your second linux, that in /usr/aarch64-unknown-linux-gnu.

/mnt/blanc/rootfs/pi is just a pi rootfs shared through nfs. you can use an intel, not just to build your own crossdev toolchain for distcc, you can also update your own toolchain and deps, and also, update the pi remotely. that is where that long command comes in. You can use it to update your toolchain in /usr/aarc64whatever. but you can also use to upgrade hard packages like gcc, remotely.

And I think you should also look into running qemu statically, using binfmt.d. Just for good measure. It's an invaluable tool. You can actually chroot on arm linux from intel cpu, seamlessly.

[eu47]

I didn't start with both systems being arm. I started just like you, building for PI on intel. It should work. I assume there is something else at fault here. NOT the different arch. And even that is not a problem as you can run cross platform through qemu-static.

I suggest you take a look in config.log to see what the actual error was.

So, after the above issue was fixed, I started to build an aarch64 clang with cross-emerge.
The dependencies were built successfully until dev-lang/python, which seems to be pulled as dependency of clang even if "python" useflag is not set.
python build fails at configure stage with:

Code: Select all

configure:25189: checking for device files
configure:25194: checking for /dev/ptmx
configure:25196: result: not set
configure:25198: error: set ac_cv_file__dev_ptmx to yes/no in your CONFIG_SITE file when cross compiling

Any idea what's the cause of this error?

[eu47]

I solved the python configure problem above by altering the ebuild:

In src_prepare I added:

Code: Select all

touch config.site
echo "ac_cv_file__dev_ptmx=no" > config.site
echo "ac_cv_file__dev_ptc=no" >> config.site

In src_configure I changed the econf line to:

Code: Select all

CONFIG_SITE=config.site econf ...