Opened 5 weeks ago

Last modified 5 weeks ago

#65477 assigned defect

iaito @5.7.0_2 +python310: Error: Failed to build iaito: command execution failed

Reported by: franetic Owned by: i0ntempest
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: monterey, x86_64 Cc:
Port: iaito


iaito fails to build on macOS 12.4. Logfile ends with

:info:build ld: framework not found Python
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build make: *** [] Error 1

Full (zipped) main.log file attached.

Attachments (1) (48.9 KB) - added by franetic 5 weeks ago.
Zipped build log from /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_iaito/iaito/main.log

Download all attachments as: .zip

Change History (4)

Changed 5 weeks ago by franetic

Attachment: added

Zipped build log from /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_iaito/iaito/main.log

comment:1 Changed 5 weeks ago by jmroot (Joshua Root)

Cc: i0ntempest@… removed
Milestone: MacPorts Future
Owner: changed from < default >i0ntempest@… to i0ntempest

comment:2 Changed 5 weeks ago by i0ntempest

Temporary workaround: select a default python with sudo port select python python310 (or whatever python variant you select).
This has to do with MacPorts Python framework does not have a Current version symlink (unless you select one with that command) and how iaito finds Python. See also: #64312

Last edited 5 weeks ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:3 Changed 5 weeks ago by franetic

Thank you for the explanation. The workaround 'worked', iaito builds successfully.

Note: See TracTickets for help on using tickets.