Some subprojects like compiler-rt define the darwin feature in their
lit config, but lld does not do that, so we need to use the global
system-darwin here instead. This test seems to have drifted from the
actual behavior so I also had to add /usr/local/lib here to make it
pass.
Details
- Reviewers
gkm thevinster - Group Reviewers
Restricted Project - Commits
- rG0885afb8b058: [lld][test] Fix darwin REQUIRES (NFC)
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lld/test/MachO/search-paths-darwin.test | ||
---|---|---|
2 | What's the reason for not supporting darwin in LLD's lit config instead? If compiler-rt defines the feature, then it makes sense for LLD to follow a similar pattern. |
lld/test/MachO/search-paths-darwin.test | ||
---|---|---|
2 | Since there are more uses of system-darwin across the whole project, and that configuration is centralized, that feels to me like a better one to standardize on. I think if we want to make this more clear for folks we should probably remove the custom ones from compiler-rt instead |
lld/test/MachO/search-paths-darwin.test | ||
---|---|---|
2 | That's fair. Fwiw, it's not just compiler-rt. A quick search showed libcxx defining the darwin feature as well, but it does look like the majority continues to use system-darwin. |
lld/test/MachO/search-paths-darwin.test | ||
---|---|---|
2 | Yea, I audited libcxx one too and the weird part about that is it uses an entirely different heuristic to enable it, and I _think_ that means we'd need to leave it separate even if we could change compiler-rt |
This breaks lld tests: http://45.33.8.238/mac/36585/step_10.txt
Please take a look and revert for now if it takes a while to fix.
Thanks for the ping, I submitted https://reviews.llvm.org/D111361, was I supposed to get an email from that failure?
What's the reason for not supporting darwin in LLD's lit config instead? If compiler-rt defines the feature, then it makes sense for LLD to follow a similar pattern.