Build of python38 @3.8.7 fails on intel Big Sur, macOS 11.1, somehow…

[ballapete (Peter "Pete" Dyballa)]

Total duration: 47.6 sec
Tests result: SUCCESS
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python38/python38/work/Python-3.8.7'
/Library/Developer/CommandLineTools/usr/bin/make build_all_merge_profile
make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python38/python38/work/Python-3.8.7'
/opt/local/bin/llvm-profdata merge -output=code.profclangd *.profclangr
error: code-30530.profclangr: Unsupported instrumentation profile format version
make[1]: *** [build_all_merge_profile] Error 1
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python38/python38/work/Python-3.8.7'
make: *** [profile-run-stamp] Error 2
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python38/python38/work/Python-3.8.7'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python38/python38/work/Python-3.8.7" && /usr/bin/make -j12 -w all
Exit code: 2

[ballapete (Peter "Pete" Dyballa)]

Main.log from intel Big Sur macOS 11.1

[ryandesign (Ryan Carsten Schmidt)]

I'm guessing that at some point you used sudo port select llvm to select some version of llvm, and that /opt/local/bin/llvm-profdata is a symlink to a program provided by that llvm port. Try using sudo port select llvm none, then sudo port clean python38 and try again and hopefully it will build this time. You can re-select your desired llvm afterward but it's of course possible it could cause similar problems again in the future.

[ballapete (Peter "Pete" Dyballa)]

This worked! Why is it necessary to select an llvm version when there is only one installed? Uninstalling llvm_select ... will break: llvm-9.0 @9.0.1_1…

[ryandesign (Ryan Carsten Schmidt)]

If you wish to be able to run llvm programs without specifying their version suffix, you use sudo port select llvm .... If you don't have a need to do that, then you can select none. You should leave the llvm_select port installed, regardless of whether or not you use sudo port select llvm .... This is the same as any other ports in MacPorts that adopt the select mechanism.

[jmroot (Joshua Root)]

The ticket doesn't mention it anywhere but this must have been with +optimizations, and would have been fixed by [4866e21854ac067f6e55ffad6c65094f3a2484ab/macports-ports], FTR.