Summary: | cross-xtensa-esp32s2-elf/gcc-10.3.0 fails due to /var/tmp/portage/cross-xtensa-esp32s2-elf/gcc-10.3.0/work/build/./gcc/as: line 106: exec: -o: invalid option | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Moon <triffid.hunter> |
Component: | Current packages | Assignee: | Cross compilation support <cross> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/tmp/portage/cross-xtensa-esp32s2-elf/gcc-10.3.0/work/build/xtensa-esp32s2-elf/libgcc/config.log
emerge --info |
Description
Michael Moon
2021-04-12 10:13:37 UTC
Created attachment 699369 [details]
emerge --info
Is your xtensa-esp32s2-elf-as binary working? Can you post the following: 1. `xtensa-esp32s2-elf-as --version` 2. `binutils-config -l` Hmm how odd, binutils-config said that xtensa-esp32s2-elf had no version selected at all, how did that happen? I'll try merging cross-xtensa-esp32s2-elf/gcc again with that fixed That seems to have it fixed - so now I'm just left wondering why it takes a few minutes before failing, and why is the error so obscure compared to the actual root cause? I suspec binutils-config (or binutils) has (or had) a bug in handling upgrade. People very rately report similar issues but it's still not clear what sequence of events is needed to lose the registration. I guess we can mark this a duplicate of that bug then - I'll report back if it happens again |