<div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 27, 2019 at 7:15 AM Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Odd. On my 10.13 machine it returns the versioned SDK. e.g.<br>
<br>
Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path<br>
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk<br>
Titan ~/Projects/MacPorts/ports > ls <br>
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs<br>
MacOSX.sdk MacOSX10.14.sdk<br>
Titan ~/Projects/MacPorts/ports > ls -lth <br>
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs<br>
total 0<br>
drwxr-xr-x 7 root wheel 224B 30 Oct 2018 MacOSX.sdk<br>
lrwxr-xr-x 1 root wheel 10B 17 Sep 2018 MacOSX10.14.sdk -> MacOSX.sdk<br>
<br>
( so yes, Xcode 10 here also only has 'macOS release + 1' SDK )<br>
<br>
what does<br>
<br>
ls -lth <br>
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs <br>
<br>
<br>
give for you ?<br>
<br>
Chris<br>
<br></blockquote><div><br></div><div>total 0<br>lrwxr-xr-x 1 root wheel 10 Sep 24 13:59 MacOSX10.14.sdk -> MacOSX.sdk/<br>drwxr-xr-x 10 root wheel 320 Sep 24 13:58 MacOSX.sdk/<br>lrwxr-xr-x 1 root wheel 10 Sep 21 10:12 MacOSX10.15.sdk -> MacOSX.sdk/<br>drwxr-xr-x 4 root wheel 128 Aug 30 02:47 DriverKit19.0.sdk/<br></div><div> </div><div>The MacOSX10.15.sdk symlink was created by the XCode 11 upgrade.</div><div>The MacOSX10.14.sdk symlink was created by me to resolve some macports issues.</div><div><br></div><div>I'm at my wits end with this. Is there some problem with the py36-pyqt5 port finding the </div><div>correct sdk?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 27/09/2019 12:11 pm, Carlo Tambuatco wrote:<br>
> On Fri, Sep 27, 2019 at 7:07 AM Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a> <br>
> <mailto:<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>>> wrote:<br>
> <br>
> what does<br>
> <br>
> xcrun --show-sdk-path<br>
> <br>
> give you ?<br>
> <br>
> <br>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk<br>
> <br>
> On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:<br>
> > I filed a ticket on this issue already and included a logfile for<br>
> it,<br>
> > but I thought there's no harm in asking the mailing list for a quick<br>
> > solution...<br>
> ><br>
> > I upgraded to macports 2.6.0 today. During a routine upgrade of my<br>
> > ports, the py36-pyqt5 port failed to configure, possibly due to a<br>
> > problem with the recent XCode 11 upgrade...?<br>
> ><br>
> > From logfile:<br>
> ><br>
> > Error: Failed to determine the detail of your Qt installation.<br>
> Try again<br>
> > using<br>
> > the --verbose flag to see more detail about the problem.<br>
> > Querying qmake about your Qt installation...<br>
> > Determining the details of your Qt installation...<br>
> > /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk<br>
> cfgtest_QtCore.pro<br>
> > Project ERROR: Could not resolve SDK Path for 'macosx10.14' using<br>
> > --show-sdk-path<br>
> ><br>
> ><br>
> > This is the first time something like this has happened. No problems<br>
> > before the XCode 11 upgrade.<br>
> ><br>
> > I upgraded to XCode 11 a few days ago, and as someone else<br>
> pointed out,<br>
> > XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.<br>
> > What I did to try and resolve it was create a MacOSX10.14.sdk<br>
> symlink.<br>
> > Is py36-pyqt5 one of those ports that has a hard-coded path to<br>
> the 10.14<br>
> > SDK, and somehow isn't fooled by the symlink I created or something?<br>
> ><br>
> ><br>
> <br>
</blockquote></div></div>