Fix linker selection: avoid LLD when using GCC with LTO#3222
Open
plop-user wants to merge 2 commits intogoogle-deepmind:mainfrom
Open
Fix linker selection: avoid LLD when using GCC with LTO#3222plop-user wants to merge 2 commits intogoogle-deepmind:mainfrom
plop-user wants to merge 2 commits intogoogle-deepmind:mainfrom
Conversation
Yashu-Maurya
approved these changes
Apr 17, 2026
|
Must needed change. Similar error in Macos |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix linker selection: avoid LLD when using GCC with LTO
Summary
MuJoCo's CMake configuration currently prioritizes linkers in the following order:
LLD→gold→bfd.This causes build failures when using GCC with LTO enabled, because LLD is selected even though it is incompatible with GCC's LTO object format.
This PR updates the linker selection logic to:
Problem
MujocoLinkOptions.cmakedetects linker support using:This test passes for LLD because:
As a result, LLD is selected and
-fuse-ld=lldis added toEXTRA_LINK_OPTIONS.Later in the build process,
MujocoOptions.cmakeenables LTO:CMAKE_INTERPROCEDURAL_OPTIMIZATION=ONThis causes GCC to compile with
-flto. LLD does not support GCC's GIMPLE IR orliblto_plugin.so. Therefore, when LLD encounters these object files, it only sees an empty.textsection. Symbols such asmainappear undefined, and linking fails.Fix
Restrict usage of LLD to Clang builds only.
Key changes:
lld(Linux/macOS) andlld-link(Windows) whenCMAKE_C_COMPILER_ID MATCHES "Clang".goldorbfd.This ensures compatibility with GCC LTO while preserving LLD usage for Clang.
Changes
Updated
MujocoLinkOptions.cmake:gold→bfd).Testing
Tested under the following configurations:
gold/bfd.python -c "import mujoco").Environment