Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-10-02 Thread Chris Jones
We are discovering, due to the Xcode 11 upgrade, just how many places in MacPorts the path to the 10.14 SDK got baked into files where we didn't mean for it to be. There are many other mailing list threads and tickets being filed with us about this. Until this is all ironed out, your

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-10-02 Thread Carlo Tambuatco
> On Sep 27, 2019, at 11:15 PM, Ryan Schmidt wrote: > > > > On Sep 27, 2019, at 06:04, Carlo Tambuatco wrote: > >> I filed a ticket on this issue already and included a logfile for it, but I >> thought there's no harm in asking the mailing list for a quick solution... >> >> I upgraded to

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Ryan Schmidt
On Sep 27, 2019, at 06:15, Chris Jones wrote: > Odd. On my 10.13 machine it returns the versioned SDK. e.g. On my 10.13 machine it also returns the versioned SDK. But on the buildbot machines, it returns the unversioned SDK, so apparently it's not that odd and doesn't indicate a problem.

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Ryan Schmidt
On Sep 27, 2019, at 06:04, Carlo Tambuatco wrote: > I filed a ticket on this issue already and included a logfile for it, but I > thought there's no harm in asking the mailing list for a quick solution... > > I upgraded to macports 2.6.0 today. During a routine upgrade of my > ports, the

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Chris Jones
doesn't look ideal On 27/09/2019 12:35 pm, Carlo Tambuatco wrote: Yeah possibly...but I just ran xcrun --show-sdk-version and got something weird: 2019-09-27 07:31:54.372 xcodebuild[33648:5774543] [MT] DVTSDK: Warning: SDK path collision for path '': SDK with name 'macosx10.15'

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Carlo Tambuatco
Yeah possibly...but I just ran xcrun --show-sdk-version and got something weird: 2019-09-27 07:31:54.372 xcodebuild[33648:5774543] [MT] DVTSDK: Warning: SDK path collision for path '': SDK with name 'macosx10.15' being superseded by SDK with 'macosx10.15'. 10.15 Is this a problem? On Fri,

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Chris Jones
I'm at my wits end with this. Is there some problem with the py36-pyqt5 port finding the correct sdk? I have no idea, but if I where you I would simplify things by first working out why xcrun --show-sdk-path is not giving you the versioned SDK path. My bet is whatever the port is doing

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Carlo Tambuatco
On Fri, Sep 27, 2019 at 7:15 AM Chris Jones wrote: > > Odd. On my 10.13 machine it returns the versioned SDK. e.g. > > Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk > Titan

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Chris Jones
Odd. On my 10.13 machine it returns the versioned SDK. e.g. Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk Titan ~/Projects/MacPorts/ports > ls

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Carlo Tambuatco
On Fri, Sep 27, 2019 at 7:07 AM Chris Jones wrote: > what does > > xcrun --show-sdk-path > > give you ? > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk > On 27/09/2019 12:04 pm, Carlo Tambuatco wrote: > > I filed a ticket on this issue already

Re: py36-pyqt5 Failed to determine details of Qt installation.

2019-09-27 Thread Chris Jones
what does xcrun --show-sdk-path 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 it, but I thought there's no harm in asking the mailing list for a quick solution... I upgraded to macports 2.6.0 today. During a