> On Jan 5, 2020, at 4:26 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >
> With what version of Xcode? > > MacPorts base doesn't allow universal builds when only the 10.14 SDK or later > are available (i.e. with Xcode 10 or later) since the SDKs don't have the > i386 parts anymore. > > https://github.com/macports/macports-base/blob/master/src/port1.0/portconfigure.tcl#L392 > > It is known that the error message shown is not worded very well to explain > this. I can't find the ticket right now. > Yes, indeed that could be relevant. I have: macOS 10.13.6 17G10021 Xcode 10.1 10B61 but I added the 10.13 SDK to support universal building: $ ls -la /Library/Developer/CommandLineTools/SDKs total 0 drwxr-xr-x 5 root wheel 160 23 Nov 17:24 . drwxr-xr-x 5 root admin 160 6 Oct 2017 .. drwxr-xr-x 7 root wheel 224 3 Nov 2018 MacOSX.sdk drwxr-xr-x 5 cunningh admin 160 9 Oct 23:54 MacOSX10.13.sdk lrwxr-xr-x 1 root wheel 10 3 Nov 2018 MacOSX10.14.sdk -> MacOSX.sdk but not in Xcode, I notice, which has been updated since I added that SDK, and in so doing has removed the SDK I had added in Xcode: $ ls -la /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs total 0 drwxr-xr-x 4 root wheel 128 3 Nov 2018 . drwxr-xr-x 5 root wheel 160 19 Oct 2018 .. drwxr-xr-x 7 root wheel 224 18 Oct 2018 MacOSX.sdk lrwxr-xr-x 1 root wheel 10 3 Nov 2018 MacOSX10.14.sdk -> MacOSX.sdk so there is an inconsistency there that might well trigger such a situation and odd error due to some baked-in path that manifests oddly. I have uninstalled all ports, and am starting the +universal build from scratch, and so far, everything is building +universal without a hiccup using that MacOS10.13.sdk. K