Summary: | Cross build of sys-dev/gcc-13.2.1_p20230826 for cross-arm-android-linux-gnueabi has a bug in gcc/as script | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Orange <crazycasta> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | cross, johannes.geiss |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | As script that has missing ORIGINAL_AS_FOR_TARGET |
Description
Alex Orange
2023-09-13 15:38:32 UTC
Created attachment 870488 [details]
As script that has missing ORIGINAL_AS_FOR_TARGET
I think I've root caused this (testing now). There was no arm-android-linux-gnueabi-as, which is why the variable wasn't set. cross-.../binutils was installed. I ran the following bit showing that binutils wasn't setup for the target in question for some reason: $ binutils-config --list-profiles [1] arm-android-linux-gnueabi-2.41 [2] arm-android-linux-gnueabihf-2.41 * [3] arm-linux-eabi-2.40 * [4] x86_64-pc-linux-gnu-2.40 * So I ran: sudo binutils-config 1 And now there's an arm-android-linux-gnueabi-as. Testing now to confirm whether gcc will compile for it (running an emerge --resume which doesn't seem to run in exactly the same order, so not sure how long it will take to get to it). This is a common issue where the GCC configure script doesn't really error out properly when it finds a tool is missing, so it ends up propagating down and just dying on a blank var when it tries to execute its value. |