[LTO] Fix System library path in LTO tests on macOS #144203
Conversation
Add explicit SDK library path (-L flag) to the System library in LTO tests to fix the "library not found for -lSystem" error on macOS. This affects the following test files: - tools/lto/print-stats.ll - tools/lto/hide-linkonce-odr.ll - tools/lto/discard-value-names.ll - tools/lto/opt-level.ll - tools/lto/no-bitcode.s The tests now explicitly include the path to the macOS SDK's usr/lib directory to ensure the linker can find the System library during test execution.
|
Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers. If you have further questions, they may be answered by the LLVM GitHub User Guide. You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums. |
Add explicit SDK library path (-L flag) to the System library in LTO tests
to fix the "library not found for -lSystem" error on macOS. This affects
the following test files:
The tests now explicitly include the path to the macOS SDK's usr/lib directory
to ensure the linker can find the System library during test execution.