macOS users, proceed with caution with Xcode v11

[MikeB]

it will probably break every MacPorts gcc version you have installed. The issue is that :

/Applications/Xcode_newX.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
Note : this is the new version 11 Xcode.app - here I added "...newX" to keep it around for a bit - but since deleted it as everything is back to normal and working again.

is missing a LOT of stuff. The simple solution is to rename Xcode.app to Xcode_old.app before installing so you can name it back to Xcode.app when you see it's totally broken. My guess is macOS 10.15 (Catalina) will be the worst macOS update since Yosemite (macOS 10.10).

That's it, forewarned is forearmed..

Note - this is on 2010 Mac Pro - so maybe that has something to do with it, but I doubt it, ymmv.

Edit - I would turn off automatic updates if you haven't already.

[bob]

I installed this yesterday. And at least for compiling crafty (using profile-guided optimizations as well) it worked flawlessly. This on a 2017-ish MacBook air.

[MikeB]

I installed this yesterday. And at least for compiling crafty (using profile-guided optimizations as well) it worked flawlessly. This on a 2017-ish MacBook air.

I have tried two more times since then, same result, breaks my terminal compilers (gcc) - not a real big deal, since I don't believe I will be migrating this 2010 Mac Pro to Catalina anyway. Each update gets hairier. I was only able to update to Mojave by upgrading the GPU anyway.

[DustyMonkey]

Are you guys testifying that Apples does not include developers in its testing?

[MikeB]

Are you guys testifying that Apples does not include developers in its testing?

Well I don’t believe that would be a true statement , but that’s a question for Apple to answer , not us.

[bob]

Apple has a very large developer group. They test continuously it seems. IE just the IOS developers have had more beta versions to test than I can count. That ignores iPadOS, macOS (MacBooks and such), Xcode and on and on...

BTW. Mike. You might try doing a full macport update including gcc. There are dependencies that might be broken with new Xcode and where it puts things... I just compiled Crafty using gcc with no issues.

[MikeB]

for anyone else shaving a similar problem as me ( missing headers under xCode 11 while staying on 10.14 ( 2010 Mac Pro does not take 10.15) , this was the fix.

https://trac.macports.org/ticket/59113? ... um_hist=11