python3.10 port does not create a symlink where other ports expect it

[mouse07410 (Mouse)]

Tried to update scons port - it failed with

.  .  .  .  .
:debug:build system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_scons/scons/work/SCons-4.3.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 setup.py --no-user-cfg build -j20 
:info:build sh: /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10: No such file or directory
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_scons/scons/work/SCons-4.3.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 setup.py --no-user-cfg build -j20 
:info:build Exit code: 127
:error:build Failed to build scons: command execution failed
:debug:build Error code: CHILDSTATUS 16594 127
: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_devel_scons/scons/main.log for details.

Reason - this port wants to find python3.10 as /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10. I don't know who's wrong - whether scons shouldn't look for Python there, or Python3.10 port should've placed there a symlink from /opt/local/bin/python3.10.

In any case, this discrepancy should be addressed/resolved.

[ryandesign (Ryan Carsten Schmidt)]

scons built successfully on all buildbot OS versions. /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 exists on my system. If it doesn't on yours, try reinstalling python310.

[mouse07410 (Mouse)]

If it doesn't on yours, try reinstalling python310

Re-installed python310. Error changed, still no success. Here's what I'm getting now:

.  .  .  .  .
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/mercurial/cext/osutil.cpython-310-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/mercurial/cext/parsers.cpython-310-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/mercurial/thirdparty/sha1dc.cpython-310-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/mercurial/thirdparty/zope/interface/_zope_interface_coptimizations.cpython-310-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/mercurial/zstd.cpython-310-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/Cython/Compiler/FlowControl.cpython-38-darwin.so: Error opening or reading file
Warning: Error parsing file /opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/Cython/Compiler/FusedNode.cpython-38-darwin.so: Error opening or reading file
.  .  .  .  .

I think I've seen that problem before, but can't recall either the context, or how we addressed it back then. And, having about 1400 ports installed, I'm not really crazy about wiping the installation out and re-building everything form scratch... :-(

[ryandesign (Ryan Carsten Schmidt)]

Hmm. Well, those are warnings, not errors, and they seem to refer to things that scons would not be using, as far as I'm aware. For example, I find no (relevant) occurrences of "mercurial" in the scons source, and I can't think of any reason why it would be using anything from python38 when I've told it to use only python310.

You could try to reinstall the ports that provide (or, if those files don't exist, should provide) those files. If you're still having problems building scons after that, please attach the main.log file from a clean build.

[jmroot (Joshua Root)]

That looks like a warning from rev-upgrade, not anything to do with scons. It means those files are registered as belonging to active ports but couldn't be opened for some reason (bad permissions, not present, etc).

[mouse07410 (Mouse)]

Not present. Which is strange... I'm very surprised.

[jmroot (Joshua Root)]

If the files were deleted after their ports were activated, deactivating then activating the ports will bring the files back. (Though as I'm sure you already realise, whatever deleted them before could do it again.)

[mouse07410 (Mouse)]

@Joshua, thanks. Though I really wonder what could possibly delete those now-missing files. I sure did not do it myself, and I don't think I run any "prune" on /opt/local... Stumped...

[jmroot (Joshua Root)]

Guess we'll close this then; please reopen if you can pin down something that MacPorts is doing wrong here.