-
-
Notifications
You must be signed in to change notification settings - Fork 12.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gcc: revision for new Xcode #45585
gcc: revision for new Xcode #45585
Conversation
It looks like |
|
Anything we can do about that? |
75781e2
to
92a9c08
Compare
On Mojave, and Mojave only:
It seems that One solution would be to force it off, configuring with |
Trying to fix by forcing the use of the SDK version that corresponds to the macOS version currently running (instead of latest SDK). |
Compiling against the 10.14 SDK on Mojave is not enough. I need someone with access to a Mojave machine to tell me what the full output of |
@fxcoudert Strange, I was able to manually change the XCode 11.0 SDK symlink to 10.14 on 10.14.5 and successfully rebuild GCC from source (as per #46393). |
@fxcoudert We've discovered that the 11.0 CLT (11.1 CLT does not exist), which the CI uses, shipped with the wrong system headers in the 10.14 SDK: #46466 (comment). The problem has been fixed in 11.2. Apparently a lot of people don't have the 11.0 CLT because Apple also botched up the update process, henced why this fix worked locally for some - they weren't using the broken CLT. |
@BrewTestBot Test this please |
This is building twice. Might want to kill the first one (I don't see how to). |
|
Requested reupload of test data for abyss in bcgsc/abyss#305. |
Now that Mojave has Xcode 11 and the 10.15 SDK, we need to update GCC there so that it fixes the system headers. Since High Sierra also now has a new Xcode version, it seems appropriate to refresh our bottles, so users avoid a mismatched GCC / Xcode / SDK combination.