Xcode update broke ports

[Richard L. Hamilton]

You might want to install it as something other than Xcode.app, like Xcode.10.3.app; you should be able to use xcode-select to pick which one has its command-line tools used.  There's another package there for the command line tools, too, I think.  Maybe someone else can better explain how to set it up so you can properly have what you need, without interfering with what you've already updated via the app store.

> On Sep 23, 2019, at 18:35, Richard L. Hamilton <rlhamil at smart.net> wrote:
> 
> Eventually MacPorts and/or Xcode will get fixed. I'm not involved except as someone else that wants it to work (I was fortunate and asked before installing it, and was warned that there might be problems). So I have no idea when "eventually" might be. Hopefully those who know more will let us know.
> 
> Until then, you can still download older Xcode versions outside of the app store, and install them:
> https://developer.apple.com/download/more/ <https://developer.apple.com/download/more/>
> 
> 10.3 is the one you want, I think.
> 
> You may need an account, although it does not have to be a paid developer account.
> 
>> On Sep 23, 2019, at 18:12, Ralph Castain <rhc at pmix.org <mailto:rhc at pmix.org>> wrote:
>> 
>> Apple apparently included an Xcode update in a recent maintenance release.
>> Since the update, I am unable to run many of the compiler ports (gcc,
>> python) due to errors stating that system headers and libraries cannot be
>> found. Investigation revealed that the ports were all configured with:
>> 
>> --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
>> 
>> However, the Xcode update apparently removed the MacOSX10.14.sdk in that directory and
>> replaced it with MacOSX10.15.sdk - even though I have NOT updated the OS
>> from Mojave!
>> 
>> I tried uninstalling all ports and reinstalling them, but that didn't
>> help. Ditto for simply creating a MacOSX10.14.sdk symlink.
>> 
>> Does anyone have a suggestion on how to get around this problem?
>> 
>> Ralph
>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20190923/1a978b44/attachment.html>