[Raspberry 3 64bit Crossdev?]

Ha, thanks!  This answers many of my questions. To be honest, using an overlay and custom ebuild is more involved than I wanted to go, specially knowing that  I will be stuck with an older crossdev anyway. Before going that route, I will try using a Gentoo docker image dedicated to distcc and / or usermode QEMU chroot env (https://github.com/sakaki-/gentoo-on-rpi3-64bit/wiki/Build-aarch64-Packages-on-your-PC%2C-with-User-Mode-QEMU-and-binfmt_misc ).

I will report my findings here so that if others follow the same route they can benefit from our shared experience.

[Raspberry 3 64bit Crossdev?]

I'm trying to setup crossdev for Aarch64 Raspberry Pi3 cross-compilation on my x64 Funtoo PC as described here.

While crossdev itself emerged ok, entering

sudo crossdev --stable -t aarch64-unknown-linux-gnu

fails after a few seconds with a rather laconic

 * error: binutils failed :(

I looked into filing a bug, as it seems this should be stable now, the closest entry dating back from 2015 but I wanted to check first if anybody had this working currently.

I've attached the files I have, as recommended by the full command output:

 * crossdev version:      20180410
 * Host Portage ARCH:     amd64
 * Target Portage ARCH:   arm64
 * Target System:         aarch64-unknown-linux-gnu
 * Stage:                 4 (C/C++ compiler)
 * USE=multilib:          no
 * ABIs:                  arm64

 * binutils:              binutils-[stable]
 * gcc:                   gcc-[stable]
 * headers:               linux-headers-[stable]
 * libc:                  glibc-[stable]

 * CROSSDEV_OVERLAY:      /usr/local/portage-crossdev
 * PORT_LOGDIR:           /var/log/portage
 * PORTAGE_CONFIGROOT:    /
 * Portage flags:         
                                                                                                                                                               
 * leaving sys-devel/binutils in /usr/local/portage-crossdev
 * leaving sys-devel/gcc in /usr/local/portage-crossdev
 * leaving sys-kernel/linux-headers in /usr/local/portage-crossdev
 * leaving sys-libs/glibc in /usr/local/portage-crossdev
 * leaving sys-devel/gdb in /usr/local/portage-crossdev
 * leaving metadata/layout.conf alone in /usr/local/portage-crossdev
                                                                                                                                                               
 * Log: /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log
 * Emerging cross-binutils ...

 * error: binutils failed :(
 *
 * If you file a bug, please attach the following logfiles:
 * /var/log/portage/cross-aarch64-unknown-linux-gnu-info.log
 * /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log.xz
 * /var/tmp/portage/cross-aarch64-unknown-linux-gnu/binutils*/temp/binutils-config.logs.tar.xz

 

cross-aarch64-unknown-linux-gnu-binutils.log.xz

cross-aarch64-unknown-linux-gnu-info.log