Re: py36-pyqt5 Failed to determine details of Qt installation.
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 simplest course of action would be to uninstall Xcode 11 and reinstall Xcode 10. Will there be a notification or something when this is all ironed out? Unlikely, as its a distributed issue, that needs fixes in numerous ports etc. There probably will not be a single moment when 'everything gets fixed' just a gradual fixing of the various issues over time. I suggest instead you add yourself to the cc list in whatever tickets are open for the ports in question you care about. https://trac.macports.org/wiki/Tickets Chris
Re: py36-pyqt5 Failed to determine details of Qt installation.
> 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 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. Try again >> using >> 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 cfgtest_QtCore.pro >> Project ERROR: Could not resolve SDK Path for 'macosx10.14' using >> --show-sdk-path >> >> >> 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 pointed out, >> 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 symlink. >> Is py36-pyqt5 one of those ports that has a hard-coded path to the 10.14 >> SDK, and somehow isn't fooled by the symlink I created or something? > > 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 simplest course > of action would be to uninstall Xcode 11 and reinstall Xcode 10. > Will there be a notification or something when this is all ironed out? > I cannot advocate creating a MacOSX10.14.sdk symlink. The 10.14 and 10.15 SDK > are not the same thing. Subverting the system into believing they are can > only cause you problems down the road. >
Re: Installing GQ
On Oct 2, 2019, at 00:57, Dave Horsfall wrote:
> (Sorry for the delay)
>
> On Sat, 18 Apr 2015, Ryan Schmidt wrote:
>
>> I've fixed this problem now. If you "sudo port selfupdate" and try again it
>> should work.
>
> No, but installing XML::Parser (or its MacPorts equivalent) fixed that error.
I'm glad you were able to work around it that way, but as I said, it is not
necessary. The correct fix is to autoreconf the affect port's configure script.
> Now...
>
> It's still failing, but with
>
>:info:build gq_display_entry_init(GQDisplayEntry* self) {}
>:info:build ^
>:info:build dt_cert.c:193:29: error: incomplete definition of type 'struct
> x509_st'
>
> Some assorted warnings, too; main.log (in GZIP) is attached (I think that's
> the correct protocol here).
>
> Is my MacBook (Sierra 10.12.6 + all patches) simply now too old to run it
> i.e. has obsolete header files?
>
> I cannot upgrade it to a later OS; it simply won't, and I've tried twice,
> failing each time with different errors so I've given up).
The openssl port has been updated to version 1.1. Many, many ports are not
compatible with this version of openssl, and it looks like you've discovered
that gq is one of them. Each such port will need to be individually
investigated and fixed.
Josh has filed a ticket for both of these problems with gq, but the maintainer
has not responded for 2 weeks, so if anyone else wants to help get it done,
please do:
https://trac.macports.org/ticket/59054
\r
