clang-20 misses “clang-rename” file

[mouse07410 (Mouse)]

Clang-20 port misses or fails to install clang-rename-mp-20 file to /opt/local/bin - as a result, port select clang mp-clang-20 fails.

In case it matters, MacOS Sequoia 15.3.1, Xcode-16.2.

[cjones051073 (Chris Jones)]

Indeed, it appears to no longer be part of clang-extra-tools

[Chris Jones <jonesc@…>]

In 433464384905074a73e5db6a6a73e683c6760177/macports-ports (master):

clang-20: clang-rename remove clang-rename from port select list
Closes: #72152

[cjones051073 (Chris Jones)]

Note I intentionally did not rev-bump above as I do not wish to force a rebuild on everyone just for this small issue (few people port select clang). It will be picked up in the next minor version update.

[mouse07410 (Mouse)]

I’m ok with your decision.

Would you mind sharing your opinion how do people that do install mp-clang-xx, actually use those ports/compilers? E.g., in my case I switch between Apple Clang and Macports Clang, keeping the selection for a while.

[cjones051073 (Chris Jones)]

You have two options.

1. Just refer to the compiler directly as the versioned MP version, e.g. clang++-mp-20 - This is what all port builds that use a MP compiler do.

2. Add the version specific install area to your path. e.g. /opt/local/libexec/llvm-20/bin - That area has all the utilities for LLVM 20 as the original unversioned names.

Honestly, there are no scenarios I really recommend port selecting LLVM. In my opinion it just confuses things as doing so masks other compilers, like the system installed versions.

[jmroot (Joshua Root)]

It would be great to switch to providing the select files in separate ports like the python ports do. But of course that change would itself require a rev bump, and so should be done in conjunction with the next version or revision update done for other reasons.