Odd. On my 10.13 machine it returns the versioned SDK. e.g.
Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path
Titan ~/Projects/MacPorts/ports > ls
Titan ~/Projects/MacPorts/ports > ls -lth
drwxr-xr-x 7 root wheel 224B 30 Oct 2018 MacOSX.sdk
lrwxr-xr-x 1 root wheel 10B 17 Sep 2018 MacOSX10.14.sdk -> MacOSX.sdk
( so yes, Xcode 10 here also only has 'macOS release + 1' SDK )
give for you ?
On 27/09/2019 12:11 pm, Carlo Tambuatco wrote:
On Fri, Sep 27, 2019 at 7:07 AM Chris Jones <jon...@hep.phy.cam.ac.uk
give you ?
On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:
> I filed a ticket on this issue already and included a logfile for
> but I thought there's no harm in asking the mailing list for a quick
> I upgraded to macports 2.6.0 today. During a routine upgrade of my
> ports, the py36-pyqt5 port failed to configure, possibly due to a
> problem with the recent XCode 11 upgrade...?
> From logfile:
> Error: Failed to determine the detail of your Qt installation.
> the --verbose flag to see more detail about the problem.
> Querying qmake about your Qt installation...
> Determining the details of your Qt installation...
> /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk
> Project ERROR: Could not resolve SDK Path for 'macosx10.14' using
> This is the first time something like this has happened. No problems
> before the XCode 11 upgrade.
> I upgraded to XCode 11 a few days ago, and as someone else
> XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.
> What I did to try and resolve it was create a MacOSX10.14.sdk
> Is py36-pyqt5 one of those ports that has a hard-coded path to
> SDK, and somehow isn't fooled by the symlink I created or something?