[MacPorts] #64579: py310-pyobjc @7.3_2 fails to build on MacOS 10.15
MacPorts
noreply at macports.org
Thu Feb 3 17:41:16 UTC 2022
#64579: py310-pyobjc @7.3_2 fails to build on MacOS 10.15
------------------------+----------------------
Reporter: Gandoon | Owner: danchr
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.7.1
Resolution: | Keywords:
Port: py-pyobjc |
------------------------+----------------------
Comment (by Gandoon):
Just a small update, I didn't mention it in the original submission, the
failure seems to occur in the ''destroot'' phase.\\
The tail end of the log file reflects this:
{{{
6885 :info:destroot Building pyobjc-core...
6886 :info:destroot Installing 'pyobjc-core' using
'/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10'
6887 :info:destroot Building pyobjc-framework-Cocoa...
6888 :info:destroot Installing 'pyobjc-framework-Cocoa' using
'/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10'
6889 :info:destroot Traceback (most recent call last):
6890 :info:destroot File
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work
/ronaldoussoren-pyobjc-4bc28cd/setup.py", line 233, in <module>
6891 :info:destroot main()
6892 :info:destroot File
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work
/ronaldoussoren-pyobjc-4bc28cd/setup.py", line 229, in main
6893 :info:destroot build_project(project, sys.argv[1:])
6894 :info:destroot File
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work
/ronaldoussoren-pyobjc-4bc28cd/setup.py", line 213, in build_project
6895 :info:destroot subprocess.check_call(
6896 :info:destroot File
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py",
line 369, in check_call
6897 :info:destroot raise CalledProcessError(retcode, cmd)
6898 :info:destroot subprocess.CalledProcessError: Command
'['/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10',
'setup.py', '--no-user-cfg', 'install', '--
prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.10', '--
root=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work/destroot']'
returned non-zero exit status 1.
6899 :info:destroot Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work/pyobjc-7.3"
&&
/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10
setup.py --no-user-cfg install
--prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.10
--root=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work/destroot
6900 :info:destroot Exit code: 1
6901 :error:destroot Failed to destroot py310-pyobjc: command execution
failed
6902 :debug:destroot Error code: CHILDSTATUS 93808 1
6903 :debug:destroot Backtrace: command execution failed
6904 :debug:destroot while executing
6905 :debug:destroot "system {*}$notty {*}$callback {*}$nice
$fullcmdstring"
6906 :debug:destroot invoked from within
6907 :debug:destroot "command_exec -callback
portprogress::target_progress_callback destroot"
6908 :debug:destroot (procedure "portdestroot::destroot_main" line
2)
6909 :debug:destroot invoked from within
6910 :debug:destroot "$procedure $targetname"
}}}
Apart from several warnings, the rest of the actual ''build'' phase seems
to have been correctly executed prior to the stopped on Error. The
`Building pyobjc-core...` initially seemed to indicate to me that a build
stage failed, but if I read the log correctly, this is indeed in the
''destroot'' phase, thus I don't think it is directly related to older
closed tickets such as #63084 or #63087, as they both failed in the
''build'' phase. Please advice if I am wrong in that assumption.
As far as I understand it, the ''destroot'' phase should perform an
''install'' procedure in the build directory, after the completion of
which the whole package is moved into its final positions. \\
Could this have something to do with which user is performing the
operation? I performed the build as root (sudo), and several of the steps
are indeed performed as or chowned to the user ''macports''.
--
Ticket URL: <https://trac.macports.org/ticket/64579#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list