I have executed `crossdev --target arm`. crossdev exit's almost imidieatly without an error description. In previous versions crossdev always outputed the step it is executing. Reproducible: Always --------------------------------------------------------------------------------------------------------------------------------------------------------------- * Host Portage ARCH: amd64 * Target Portage ARCH: arm * Target System: arm-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /usr/local/portage/layman/thelinux * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/arm-unknown-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/arm-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ...
Created attachment 228611 [details] /var/log/portage/cross-arm-unknown-linux-gnu-info.log
The actual output is this one: --------------------------------------------------------------------------------------------------------------------------------------------------------------- * Host Portage ARCH: amd64 * Target Portage ARCH: arm * Target System: arm-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /usr/local/portage/layman/thelinux * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/arm-unknown-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/arm-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ !! ]
I figured out, some distfiles were missing in the mirror. crossdev should have at least given a log file, where I could read what was wrong.
Which version of crossdev?
you can find the info yourself by doing `emerge {binutils,gcc}-config`. i dont think it's really worth adding infrastructure to fix -- read the logs emerge itself produces.