This is an archive of the discontinued LLVM Phabricator instance.

[clang] Only use major version in resource dir
ClosedPublic

Authored by tbaeder on May 18 2022, 1:21 AM.

Diff Detail

Event Timeline

tbaeder created this revision.May 18 2022, 1:21 AM
Herald added a project: Restricted Project. · View Herald Transcript
Herald added a subscriber: mgorny. · View Herald Transcript
tbaeder requested review of this revision.May 18 2022, 1:21 AM
Herald added projects: Restricted Project, Restricted Project, Restricted Project, Restricted Project, Restricted Project. · View Herald TranscriptMay 18 2022, 1:21 AM
tbaeder updated this revision to Diff 435850.Jun 10 2022, 3:17 AM
tbaeder updated this revision to Diff 435876.Jun 10 2022, 5:11 AM

To be honest, I've never seen much purpose in the x.y.z directory naming and I feel like it's making packaging unnecessarily more complex, at least for us in Gentoo.

That said, I'd personally prefer if the directory was entirely configurable just like CLANG_RESOURCE_DIR can specify arbitrary path right now. But I'm also fine with this as-is.

Adding some more people who may have an opinion.

The consensus in the discourse thread you mention is not super strong, but I tend to agree with that patch. +1 for me.

i hope not too many people rely on it.
LGTM but please add it to the release notes

tbaeder updated this revision to Diff 473208.Nov 4 2022, 6:04 AM
MaskRay accepted this revision.Nov 4 2022, 7:30 PM

LGTM. Considering https://discourse.llvm.org/t/should-we-continue-embed-the-full-llvm-version-in-lib-clang/62094 and this thread, I think overall people favor this patch.

If a distribution wants to provide 16.0 and 16.1 simultaneously, the two installations can be in different install prefixes :)

This revision is now accepted and ready to land.Nov 4 2022, 7:30 PM
tbaeder updated this revision to Diff 473951.Nov 8 2022, 3:54 AM

Add a release note

serge-sans-paille accepted this revision.Nov 8 2022, 4:52 AM

I'm worried that this is gonna break build bots. Has anyone seen the ThreadSanitizer timeout reported by the precommit-ci before?

@tbaeder That CI failure seems unrelated. Maybe just commit early in the day so you have time to deal with the bot failures (if any).

This revision was landed with ongoing or failed builds.Nov 10 2022, 6:02 AM
This revision was automatically updated to reflect the committed changes.