Opened 16 months ago
Closed 15 months ago
#66611 closed defect (fixed)
py311-pyqt5 configure error on 10.13.6, ports 2.8.0
| Reported by: | rufty (Bill Hill) | Owned by: | reneeotten (Renee Otten) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | sdk-path pyqt5 | Cc: | |
| Port: | py311-pyqt5 |
Description
Trying to install py311-pyqt5 (I've got py310-pyqt5 installed since some while ago.)
Getting a configure error:
"ERROR: Could not resolve SDK Path for 'macosx10.13' using --show-sdk-path"
And:
xcrun --show-sdk-path
Gives:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
Is this the port or my Xcode?
Attachments (1)
Change History (7)
Changed 16 months ago by rufty (Bill Hill)
| Attachment: | py311-pyqt5.log added |
|---|
comment:1 Changed 16 months ago by jmroot (Joshua Root)
| Owner: | set to reneeotten |
|---|---|
| Status: | new → assigned |
comment:2 Changed 16 months ago by reneeotten (Renee Otten)
comment:3 Changed 16 months ago by kencu (Ken)
this is likely happening because the user is on 10.13, but apparently has only a MacOSX10.14.sdk in the SDKs folder.
MacPorts works best having a system-matching SDK available in the two needed locations, otherwise issues such as this can arise.
comment:4 Changed 16 months ago by reneeotten (Renee Otten)
@kencu: can you remind us how to resolve this issue?! I do remember it’s a common problem/user mistake but being on my cellphone I have a hard time finding the way how to resolve this…
comment:5 Changed 15 months ago by rufty (Bill Hill)
Nasty work-around - go as far as possible, until it errors out.
sudo vim \ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-pyqt5/py311-pyqt5/work/PyQt5-5.15.7/.qmake.cache
Continue build, destroot, install
comment:6 Changed 15 months ago by reneeotten (Renee Otten)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
this could be a duplicate of 66589. I am currently traveling and abroad - will likely not get to this within the next week. Perhaps it’s as simple as an update of
py-pyqt-builderto resolve this. Last time I looked at this there were some issues with older Python versions but I’m sure there is some way to get that port up-to-date again.