Opened 5 months ago

Last modified 3 months ago

#64122 new defect

Sphinx build fails on Monterey with Apple Sillicon

Reported by: ndebarnot (Nero) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: sphinx

Description

Installation of sphinx port fails with the following error:

--->  Creating launchd control script 'sphinx'
Error: Failed to destroot sphinx: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_sphinx/sphinx/work/sphinx-2.2.11-release/org.macports.sphinx.plist" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_sphinx/sphinx/work/destroot/opt/local/etc/LaunchDaemons/org.macports.sphinx/org.macports.sphinx.plist": file already exists
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_sphinx/sphinx/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port sphinx failed

Change History (3)

comment:1 Changed 5 months ago by ndebarnot (Nero)

Summary: Sphinx build fails on Montery with Apple SilliconSphinx build fails on Monterey with Apple Sillicon

comment:2 Changed 5 months ago by ryandesign (Ryan Schmidt)

Keywords: sphinx removed

This port both uses startupitem.create (which creates a launchd plist) and also tries to create and install a launchd plist manually. Seems like the port should choose just one method of installing the plist.

MacPorts base recently changed when launchd plists created by startupitem.create are placed into the destroot. They used to be created after the destroot phase; now they are created before the destroot phase, on order to give ports and opportunity to modify them if needed.

comment:3 Changed 3 months ago by ndebarnot (Nero)

Hello,

It looks like we're still unable to install Sphinx on Apple Silicon / Mac OS Monterey. Does anybody know if this will be fixed in the near future?

Thanks!

Note: See TracTickets for help on using tickets.