#63751 closed defect (fixed)
spice-gtk @0.39 Python module pyparsing not found - Monterey arm64 and x86_64
Reported by: | soundpassion | Owned by: | reneeotten (Renee Otten) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | ||
Port: | spice-gtk |
Description
Hi all,
during the build of the port of spice-gtk I got this error:
Error: Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build/meson-logs/meson-log.txt Error: Failed to configure spice-gtk: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details.
on meson-log.txt:
Message: Checking for python module pyparsing Running command: /opt/local/bin/python3.9 -m pyparsing --- stdout --- --- stderr --- /opt/local/bin/python3.9: No module named pyparsing.__main__; 'pyparsing' is a package and cannot be directly executed subprojects/spice-common/meson.build:137:8: ERROR: Problem encountered: Python module pyparsing not found
on main.log
:info:configure spice-common| Message: Checking for python module pyparsing :info:configure subprojects/spice-common/meson.build:137:8: ERROR: Problem encountered: Python module pyparsing not found :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build/meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice-gtk-0.39" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice-gtk-0.39 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build/meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname"
Thanks for the support
both logs and py39-parsing module files check image attached.
Best regards
Attachments (1)
Change History (10)
Changed 3 years ago by soundpassion
Attachment: | Archive.zip added |
---|
comment:1 Changed 3 years ago by PeteToscano (Pete Toscano)
comment:3 Changed 3 years ago by soundpassion
Summary: | spice-gtk @0.39 Python module pyparsing not found - Monterey arm64 → spice-gtk @0.39 Python module pyparsing not found - Monterey arm64 intel64 |
---|
comment:4 Changed 3 years ago by soundpassion
Summary: | spice-gtk @0.39 Python module pyparsing not found - Monterey arm64 intel64 → spice-gtk @0.39 Python module pyparsing not found - Monterey arm64 and x86_64 |
---|
comment:5 Changed 3 years ago by reneeotten (Renee Otten)
problem appears to be that the check that meson does python -m pyparsing
errors out with the current version (3.0.4) of py-parsing
which didn't happen with the latest version in the 2.x branch. So this is likely not related to Monterey and will probably fail everywhere now.
This is an upstream issue and should be reported there (perhaps they've fixed it already; I looked briefly but didn't see the source code/version control system easily). Alternatively, one could probably patch out the check since we they're listed as dependencies and therefore installed anyway. Of course the question remains whether it is compatible with the 3.x version of pyparsing.
comment:6 Changed 3 years ago by reneeotten (Renee Otten)
upstream bug report: https://gitlab.freedesktop.org/spice/spice-common/-/issues/5
comment:7 Changed 3 years ago by reneeotten (Renee Otten)
Owner: | set to reneeotten |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I see the same error on Intel.