Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#65576 closed defect (duplicate)

Error: Failed to build py39-pyqt5: command execution failed

Reported by: adamgao1996 Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: Oscarabranches
Port: py39-pyqt5

Description

macOS12.5 M1

:info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtSql bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtSql.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtSvg bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtSvg.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtTest bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtTest.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtTextToSpeech bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtTextToSpeech.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtWebChannel bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtWebChannel.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtWebSockets bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtWebSockets.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtWinExtras bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtWinExtras.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtX11Extras bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtX11Extras.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtXml bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtXml.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the QtXmlPatterns bindings can be built... :info:build /opt/local/libexec/qt5/bin/qmake QtXmlPatterns.pro :info:build Project ERROR: Could not resolve SDK Path for 'macosx12' using --show-sdk-path :info:build Checking to see if the dbus-python support should be built... :info:build pkg-config --cflags-only-I --libs dbus-1 :info:build These bindings will be built: Qt, pylupdate, pyrcc. :info:build Generating the Qt bindings... :info:build Generating the pylupdate bindings... :info:build sip-build-3.9: Q_PID is undefined :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-pyqt5/py39-pyqt5/work/PyQt5-5.15.7" && sip-build-3.9 --qmake /opt/local/libexec/qt5/bin/qmake --verbose --confirm-license --dbus=/opt/local/Library/Frameworks/Python.framework/Versions/3.9/include/python3.9/dbus-1.0 --disable QtWebKit --disable QtWebKitWidgets :info:build Exit code: 1 :error:build Failed to build py39-pyqt5: command execution failed :debug:build Error code: CHILDSTATUS 83248 1 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-pyqt5/py39-pyqt5/main.log for details.

Change History (5)

comment:1 Changed 2 years ago by chrstphrchvz (Christopher Chavez)

Duplicate of #65410

comment:2 Changed 2 years ago by Oscarabranches

I am new to MacPorts

I am also facing the same issue.

It appears that the servers holding this module are not available or down.

Kindly look into it

Oscar

comment:3 Changed 2 years ago by Oscarabranches

Cc: Oscarabranches added

comment:4 in reply to:  1 Changed 2 years ago by mascguy (Christopher Nielsen)

Resolution: duplicate
Status: newclosed

Replying to chrstphrchvz:

Duplicate of #65410

I added you folks to the original ticket, which @chrstphrchvz mentioned.

comment:5 Changed 2 years ago by Oscarabranches

Thank You.

Note: See TracTickets for help on using tickets.