Opened 6 months ago

Last modified 3 weeks ago

#63778 new defect

gcc10: Error: configuring for an unreleased macOS version x86_64-apple-darwin21

Reported by: astroboylrx (Rixin Li) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: monterey Cc: ballapete (Peter "Pete" Dyballa), cooljeanius (Eric Gallager)
Port: gcc10

Description

gcc10 failed to configure on macOS Monterey. The attached main.log shows

:info:build Error: configuring for an unreleased macOS version x86_64-apple-darwin21
:info:build make[2]: *** [configure-stage1-gcc] Error 1

Attachments (1)

main.log.zip (39.3 KB) - added by astroboylrx (Rixin Li) 6 months ago.
full log of installing gcc10

Download all attachments as: .zip

Change History (6)

Changed 6 months ago by astroboylrx (Rixin Li)

Attachment: main.log.zip added

full log of installing gcc10

comment:1 Changed 6 months ago by ryandesign (Ryan Schmidt)

Keywords: monterey added; gcc10 Monterey darwin21 removed
Priority: HighNormal
Summary: gcc10 failed to configure on macOS Montereygcc10: Error: configuring for an unreleased macOS version x86_64-apple-darwin21
Version: 2.7.02.7.1

comment:2 Changed 6 months ago by ballapete (Peter "Pete" Dyballa)

Cc: ballapete added

comment:3 Changed 5 months ago by davidvogan

This first error "Error: configuring for an unreleased macOS version x86_64-apple-darwin21" traces to the file

gcc-10.3.0/gcc/config.gcc

Lines 677-719 run through various possibilities for the Mac OS; but they stop at Darwin 20. After line 690, there should be an additional case like

*-*-darwin21*)

# Darwin 21 corresponds to macOS 12. macos_maj=12 ;;

When I made this change (probably clumsily or incorrectly), compilation proceeded past this first error, but failed on the second:

:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[3]: * [build/gencondmd] Error 1

which referred to a long list of undefined symbols

:info:build Undefined symbols for architecture x86_64: :info:build "_cfun", referenced from:...

No idea how to address that.

comment:4 Changed 5 months ago by kencu (Ken)

Your most effective method of resolving issues with gcc-10 (or, to be honest, most any gcc) on darwin at this moment in time is probably to go here:

https://github.com/iains/gcc-10-branch

and open an issue in this github branch directly with the gcc darwin maintainer. Most likely, he has already fixed it and can point you to the exact commit you need.

If not, if he has time, he will generally be very happy to try to work through a proper fix for you, and then it will be upstreamed in due course if it works out.

There is a separate gcc bug tracking system of course. It is possible that Iain might send you there to open a ticket instead, but lately he has been most responsive there on github in the gcc repos he is working with.

comment:5 Changed 3 weeks ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.