Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 753380

Summary: sys-devel/clang should put run-clang-tidy into PATH
Product: Gentoo Linux Reporter: Florian Schmaus <flo>
Component: Current packagesAssignee: LLVM support project <llvm>
Status: UNCONFIRMED ---    
Severity: normal CC: jstein, mgorny
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Florian Schmaus 2020-11-06 19:43:07 UTC
The sys-devel/clang ebuild(s) should put run-clang-tidy into PATH. Some tools behave differently whether or not run-clang-tidy is in PATH. For example Meson (dev-util/meson) will fall back to a direct clang-tidy invocation if run-clang-tidy is not in PATH [1].


1: https://github.com/mesonbuild/meson/blob/cc033e5476b40a97662f15af1736262371738e50/mesonbuild/scripts/clangtidy.py#L51

Reproducible: Always
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2020-11-06 20:43:35 UTC
We're installing it where upstream installs it.  You should talk to LLVM people to change the install location, or ask Meson people why they rely on random downstream changes.
Comment 2 Florian Schmaus 2020-11-06 22:09:58 UTC
Understood, created https://reviews.llvm.org/D90972

> or ask Meson people why they rely on random downstream changes.

I am not sure what this is supposed to mean? Meson has no other chance to figure out if run-clang-tidy(.py) is available besides looking it up in $PATH. Hence I think the ideal solution would be upstream changing the install location of run-clang-tidy.py from share/clang/ to bin/.