update GCC10 to accept MACOSX_DEPLOYMENT_TARGET to be 11.0

[vdoublie]

gcc10 fails to build because it is confused by deployment target to be 11.0 hence the configuration is incorrect it fails to find specific library locations.

xgcc: warning: couldn't understand version 11.0

ld: library not found for -lgcc_s.10.4

in the config: because it cannot deal with 11.0 version it falls back to lowest possible OS version 10.4

[vdoublie]

tgz file of the main log file for the build of libgcc10

[kencu (Ken)]

yup. hard coded to assume major version is 10 here <​https://github.com/gcc-mirror/gcc/blob/7355a9408b990cdd20db91e2e1ba0b03e801d6a6/gcc/config/darwin-c.c#L695> with fallback to oldest system. maybe there are other places this is done as well.

this is totally an upstream issue, it would seem. I did not notice the gcc bug report about it yet.

[vdoublie]

it shows up once user upgrades to 11.0b3 and xc. 12b3 b2's remain 10.16 and all is good

[kencu (Ken)]

taking a quick look, if you just removed that sanity test it might just work:

if (version_array[MAJOR] != 10)
    goto fail;

Edit: no, that would not be enough. The function needs to be rewritten with major versions other than 10 to be covered.

[vdoublie]

The issues are deep than expected. a quick fix in Darwin-c.c and Darwin-driver.c to accept 11.0 help through this. leads to deep issue : see log undefined functions in libcc1plugin.o

[vdoublie]

after fix in darwin-c.c and Darwin-driver.c

[kencu (Ken)]

Your best bet here is to find &/or open a gcc bug report to track this, and work on it there. There will be many other people interested, but they won't find this ticket here to work on it with you. Homebrew, Fink, casual users, and MacPorters are all involved.

[vdoublie]

will do asap

[vdoublie]

issue is not just gcc10. Many configure files do not contain cases for macOS 11.0* and Xcode 12.0*

patches as attached

[vdoublie]

patches configure files missing cases for macOS 11,0

[vdoublie]

I wil send the patches to gcc10 dev people

[bigmoe]

I have reproduced this issue on the public release version of macOS 11.0.1.

Are gcc10 devs aware of this? I couldn't find any reports on their bug tracker.

[kencu (Ken)]

They are. This has been fixed in a repo run by the Darwin lead for gcc. It is not ready yet for public consumption, but if you're adventuresome, here it is, along with a nascent ARM64 port of gcc:

<​https://github.com/iains/gcc-darwin-arm64>

[kencu (Ken)]

BTW, if you think we should make a new gcc port use that fork for now, or move gcc-devel to use it -- we're ahead of you :>

It just plain doesn't work yet, but there are people working on it.

[cjones051073 (Chris Jones)]

The repo above is not required to fix things for macOS 11 running on Intel. The patches above work fine on this arch so I think I will commit these to at least get gcc10 working on Intel.

Fixing things for Apple Silicon is an entirely different issue, tbh.

[Chris Jones <jonesc@…>]

In 53ad57cd08c5971b5a92df34d84e62589bc006b4/macports-ports (master):

(lib)gcc10: Add patches to support building against 11.0 SDK
Closes: #60908

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #61399, #61456.