Xcode and gcc conflict: resolved soon?

Chris Jones jonesc at hep.phy.cam.ac.uk
Fri Oct 4 16:23:20 UTC 2019


Please always provide the exact error messages when reporting problems, 
otherwise it is difficult to know exactly what you are referring. There 
are a number of different issues at the moment w.r.t. Xcode 11.

That said, its probably not possible at this point to give you a 
timescale when everything will be fixed with Xcode 11, partly because a 
number of the issues are beyond macPorts control, and require fixes from 
upstream (or perhaps even from Apple for Xcode itself).

So yes, at this point if you do not wish to have to deal with or help 
fix these issues, you should downgrade Xcode back to 10.x.


On 04/10/2019 4:19 pm, Thomas Ruedas wrote:
> Hi,
> I made the mistake of upgrading Xcode to the latest version (11.0), 
> where Apple seems to have introduced stuff that breaks a lot of things. 
> Among these, it seems, is gcc9. More specifically, when I tried to 
> upgrade outdated ports, a number of them could not be compiled, such as 
> poppler and openblas, and the discussions in the newsgroups indicate 
> that it has to do with the new Xcode.
> Is there reason to expect that this conflict, specifically the problems 
> with gcc9 and with openblas, are resolved in the new future, or should I 
> try to go back to the old Xcode?
> Thomas
> PS: I am on the latest Mojave.

More information about the macports-users mailing list