[HIP] hipcc.pl assumes Clang++ is always called 'clang++' about chipstar HOT 8 CLOSED

Do these packages not create a symlink to clang++-14 -> clang++ as is the case when installing LLVM from source?

from chipstar.

Not by default (it seems) as it's common to use multiple different versions in the same system.

from chipstar.

There is a symlink to clang++ but the clang++ itself resides in /usr/lib/llvm-14/bin/ [source].

from chipstar.

Symlink to clang++-14 to be accurate. Paulius was hoping there would be a clang++ symlink since the script assumes the executable to be called 'clang++'. Perhaps this can be set up with the 'update-alternatives' mechanism of Ubuntu, but I think a more robust way is to refer to the exact path of the Clang++ binary to be used since there are major incompatibilities between versions.

from chipstar.

but I think a more robust way is to refer to the exact path of the Clang++

Current HIP_CLANG_PATH refers to the directory path where it will look for clang++ I will make the change to for HIP_CLANG_PATH to require a full path to the binary.

from chipstar.

HIPAMD currently also expects clang++. In the next release we will be migrating to C++ based hipcc and this Perl script will be deprecated. Let's make this change then. In the meantime, if using Ubuntu the user should just make a symlink.

from chipstar.

OK, it would be good to at least document this in README.md or even check in cmake time?

from chipstar.

I will make a note in README.md

from chipstar.