Bug 912872 – =cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7 does fail to setup with: sys-devel/crossdev to build a musl toolchain

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description tt_1 2023-08-23 13:05:06 UTC]

this is the command used: 

crossdev -S -L aarch64-unknown-linux-musl --ov-output /var/db/repos/local/

this is from the log: 


cat /var/log/portage/cross_llvm-aarch64-unknown-linux-musl-musl-headers.log

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local
 * musl-1.2.3.tar.gz BLAKE2B SHA512 size ;-) ...                         [ ok ]
 * getconf.c BLAKE2B SHA512 size ;-) ...                                 [ ok ]
 * musl-getent-93a08815f8598db442d8b766b463d0150ed8e2ab.c BLAKE2B SHA512 size ;-) ...            [ ok ]
 * iconv.c BLAKE2B SHA512 size ;-) ...                                   [ ok ]
 * ERROR: cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local failed (setup phase):
 *   Use sys-devel/crossdev to build a musl toolchain
 * 
 * Call stack:
 *              ebuild.sh, line 136:  Called pkg_setup
 *   musl-1.2.3-r7.ebuild, line  71:  Called die
 * The specific snippet of code:
 *   		*) die "Use sys-devel/crossdev to build a musl toolchain" ;;
 * 
 * If you need support, post the output of `emerge --info '=cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local'`,
 * the complete build log and the output of `emerge -pqv '=cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local'`.
 * The complete build log is located at '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/temp/die.env'.
 * Working directory: '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/empty'
 * S: '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/work/musl-1.2.3'

>>> Failed to emerge cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7, Log file:

>>>  '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/temp/build.log'
 * Messages for package cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7:
 * ERROR: cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local failed (setup phase):
 *   Use sys-devel/crossdev to build a musl toolchain
 * 
 * Call stack:
 *              ebuild.sh, line 136:  Called pkg_setup
 *   musl-1.2.3-r7.ebuild, line  71:  Called die
 * The specific snippet of code:
 *   		*) die "Use sys-devel/crossdev to build a musl toolchain" ;;
 * 
 * If you need support, post the output of `emerge --info '=cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local'`,
 * the complete build log and the output of `emerge -pqv '=cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7::local'`.
 * The complete build log is located at '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/temp/die.env'.
 * Working directory: '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/empty'
 * S: '/var/tmp/portage/cross_llvm-aarch64-unknown-linux-musl/musl-1.2.3-r7/work/musl-1.2.3'

[Comment 1 tt_1 2023-08-23 13:05:49 UTC]

Created attachment 868525 [details]
output from emerge --info

[Comment 2 Alfred Persson 2023-08-23 13:32:30 UTC]

Hey! It only supports musl-1.2.4 and -9999 currently. "aarch64-gentoo-linux-musl" works here, but "aarch64-unknown-linux-musl" should work too

[Comment 3 Sam James 2023-08-23 13:32:49 UTC]

Need to use ~arch musl for now.

[Comment 4 tt_1 2023-08-23 16:48:34 UTC]

(In reply to Alfred Persson from comment #2)
> Hey! It only supports musl-1.2.4 and -9999 currently.
> "aarch64-gentoo-linux-musl" works here, but "aarch64-unknown-linux-musl"
> should work too

indeed, need to take musl-1.2.4 and both targets work

there is no check for sys-devel/lld on host yet 

also cross-emerge doesn't seem to work