Open stefson opened 4 years ago
the double generated target.armv7(a) in the config.toml might be from an error in the false detection of armv7a-unknown-linux-musleabihf as multilib?
first problem can be solved by unmasking thumb2 mask, and also I believe to have found the line which causes the double entry of armv7+armv7a. Right now the patched up ebuild still compiles, but config.toml seemed to be okay. Will publish diff file in the next days.
cpu_flags_arm_thumbv2 is masked:
musl-box / # emerge -pv =rust-1.41.1
These are the packages that would be merged, in order:
[ebuild U #] dev-lang/rust-1.41.1:stable/1.41::musl [1.34.2:stable/1.34::musl] USE="-clippy -debug -doc -libressl -miri% -nightly% -parallel-compiler% -rls -rustfmt -system-bootstrap% -system-llvm -wasm%" CPU_FLAGS_ARM="neon% (-thumb2)" LLVM_TARGETS="(ARM) -AArch64 -AMDGPU -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV% -Sparc -SystemZ -WebAssembly -X86 -XCore" 0 KiB
and with only cpu_flags_arm_neon available there's nothing happening during src_configure: