https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Mark Mentovai from comment #20) > Created attachment 59189 [details] > Patch for macOS 14/Xcode 16 > > (In reply to GCC Commits from comment #19) > > The master branch has been updated by Iain D Sandoe <ia...@gcc.gnu.org>: > > > > https://gcc.gnu.org/g:d9cafa0c4f0a81304d9b95a78ccc8e9003c6d7a3 > > > > commit r15-3839-gd9cafa0c4f0a81304d9b95a78ccc8e9003c6d7a3 > > Author: Iain Sandoe <i...@sandoe.co.uk> > > Date: Sun Sep 22 11:43:32 2024 +0100 > > > > libgcc, Darwin: Drop the legacy library build for macOS >= 15 > > [PR116809]. > > Unfortunately, this doesn’t resolve the bug in every place that it might be > encountered. > > The bootstrapping problem occurs when targeting x86_64 and using the macOS > 15 SDK. The macOS 15 SDK ships in Xcode 16, which also runs on macOS 14. > libgcc_s.1 can no longer be built on macOS 14 using Xcode 16 by the same > logic that the above change disabled it for macOS 15. Thta is quite surprising - since the SDK should reflect the symbols exported by the libraries installed on the target system. Therefore, they should be present when the target is macOS 14; Perhaps something not conditional in the way it should be - or it is depending on support for attribute ((availability)) which is only currently committed on darwin branches. If we build a compiler targeting macOS 15, but using xcode 16 on macOS 14 - then we should still eliminate the library.
