| Summary: | sys-devel/crossdev fail to generate aarch64-unknown-linux-gnu toolchain | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Yixun Lan <dlan> |
| Component: | Current packages | Assignee: | Gentoo Crossdev team <crossdev> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | embedded, jstein, vapier |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 627914 | ||
| Attachments: |
cross-aarch64-unknown-linux-gnu-gcc-stage1.log.xz
gcc-config.logs.tar.xz cross-aarch64-unknown-linux-gnu-info.log |
||
Created attachment 472752 [details]
gcc-config.logs.tar.xz
Created attachment 472754 [details]
cross-aarch64-unknown-linux-gnu-info.log
Essentially the same command just worked for me a couple weeks ago: crossdev -v -t aarch64-unknown-linux-gnu --ex-gdb --ov-output /usr/local/armv8 The one thing I always do is disable any local overlays for crossdev builds and point it to its own overlay dir (also I always use crossdev-99999999). It's actually armv7a that fails now on glibc if gcc version is greater than or equal to 6.x Oh, and try it again without the cross- in the target name. Yes, it should be 'crossdev -t aarch64-unknown-linux-gnu' without 'cross-' prefix. |
Created attachment 472750 [details] cross-aarch64-unknown-linux-gnu-gcc-stage1.log.xz ofmlt ~ # crossdev -t cross-aarch64-unknown-linux-gnu ------------------------------------------------------------------------------------------------ * crossdev version: 8b1b79e02cc36bc6f2b5583db6aeea333fb8d59b * Host Portage ARCH: amd64 * Target Portage ARCH: arm64 * Target System: aarch64-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * ABIs: arm64 * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * CROSSDEV_OVERLAY: /var/lib/layman/local * PORT_LOGDIR: /var/log/portage/build * PORTAGE_CONFIGROOT: * Portage flags: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * leaving sys-devel/binutils in /var/lib/layman/local * leaving sys-devel/gcc in /var/lib/layman/local * leaving sys-kernel/linux-headers in /var/lib/layman/local * leaving sys-libs/glibc in /var/lib/layman/local * leaving sys-devel/gdb in /var/lib/layman/local * enabling thin-manifests due to /var/lib/layman/kde _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Log: /var/log/portage/build/cross-aarch64-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/build/cross-aarch64-unknown-linux-gnu-linux-headers-quick.log * Emerging cross-linux-headers-quick ... [ ok ] * Log: /var/log/portage/build/cross-aarch64-unknown-linux-gnu-glibc-headers.log * Emerging cross-glibc-headers ... [ ok ] * Log: /var/log/portage/build/cross-aarch64-unknown-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... * error: gcc failed :( * * If you file a bug, please attach the following logfiles: * /var/log/portage/build/cross-aarch64-unknown-linux-gnu-info.log * /var/log/portage/build/cross-aarch64-unknown-linux-gnu-gcc-stage1.log.xz * /var/tmp/portage/cross-aarch64-unknown-linux-gnu/gcc*/temp/gcc-config.logs.tar.xz