Opened 2 weeks ago

Last modified 13 days ago

#62719 new defect

arm-none-eabi-gcc fails to build on M1

Reported by: hpux735 (William Dillon) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: arm64, bigsur Cc:
Port: arm-none-eabi-gcc

Description


Attachments (1)

main.log (36.3 KB) - added by hpux735 (William Dillon) 2 weeks ago.
port logs

Download all attachments as: .zip

Change History (7)

Changed 2 weeks ago by hpux735 (William Dillon)

Attachment: main.log added

port logs

comment:1 Changed 2 weeks ago by hpux735 (William Dillon)

It looks like this might be the upstream bug?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865

comment:2 Changed 2 weeks ago by ryandesign (Ryan Schmidt)

Yes, that looks like the bug. A common problem with many ports on Big Sur and later. (Any software using libtool and relying on undefined symbols.) Looks like gcc went a slightly different direction with the fix from the one that we usually apply, which is the one I described in the upstream libtool bug report which the developers of libtool have yet to acknowledge.

comment:3 Changed 2 weeks ago by hpux735 (William Dillon)

Ah, very interesting. Thanks. Is this something that'll be blocked indefinitely until it's done upstream, or is it something that can be patched in the port files?

comment:4 Changed 2 weeks ago by ryandesign (Ryan Schmidt)

We should update arm-none-eabi-gcc to the latest version, which is 10.3.0. Maybe that already incorporates the fix. If not, or if updating is too difficult, we can apply a patch.

Note that "we" means any interested volunteer. This port has no maintainer.

comment:5 Changed 2 weeks ago by hpux735 (William Dillon)

Ok, I can give it a shot. Just so long as you don't mind me asking questions on this bug if I get stuck

comment:6 Changed 13 days ago by hpux735 (William Dillon)

So I see your patch, and that makes sense. Where I'm a little stuck is that the portfiles for the cross tools are all made with that tcl script, and I'm not really familiar with how to "hook" into it. Do you have any advice?

Note: See TracTickets for help on using tickets.