Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 753380 - sys-devel/clang should put run-clang-tidy into PATH
Summary: sys-devel/clang should put run-clang-tidy into PATH
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: LLVM support project
Depends on:
Reported: 2020-11-06 19:43 UTC by Florian Schmaus
Modified: 2020-11-06 22:09 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Florian Schmaus gentoo-dev 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].


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 gentoo-dev 2020-11-06 22:09:58 UTC
Understood, created

> 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 from share/clang/ to bin/.