Skip to content

Failed to link libclangTesting.so.21.0git: undefined symbol: llvm::Triple::Triple #130112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
carlosgalvezp opened this issue Mar 6, 2025 · 2 comments · Fixed by #130105
Closed

Comments

@carlosgalvezp
Copy link
Contributor

carlosgalvezp commented Mar 6, 2025

Hi!

I'm bumping by local clone of the repo since ~700 commits ago, and now when trying to ninja check-clang-tools, I get:

ld.lld: error: undefined symbol: llvm::Triple::Triple(llvm::Twine const&)
>>> referenced by CommandLineArgs.cpp
>>>               tools/clang/lib/Testing/CMakeFiles/clangTesting.dir/CommandLineArgs.cpp.o:(clang::getAnyTargetForTesting[abi:cxx11]())

I've tried a clean build and get the same result. Is this issue known?

Platform: Ubuntu 20.04, compiling with clang 20

@carlosgalvezp
Copy link
Contributor Author

Bisecting leads me here: 979c275
@nikic

@nikic
Copy link
Contributor

nikic commented Mar 6, 2025

There is a fix here: #130105

VishMCW pushed a commit to VishMCW/llvm-project that referenced this issue Mar 18, 2025
llvm#130105)

…etParser from clangTesting

Commit 979c275 (llvm#129868) introduced a
dependency on the llvm::Triple::Triple in `lookupTarget`. This is part
of TargetParser, which wasn't listed in
clang/lib/Testing/CMakeLists.txt. This broke the
-DBUILD_SHARED_LIBS=True builds.

Fixes llvm#130112
jph-13 pushed a commit to jph-13/llvm-project that referenced this issue Mar 21, 2025
llvm#130105)

…etParser from clangTesting

Commit 979c275 (llvm#129868) introduced a
dependency on the llvm::Triple::Triple in `lookupTarget`. This is part
of TargetParser, which wasn't listed in
clang/lib/Testing/CMakeLists.txt. This broke the
-DBUILD_SHARED_LIBS=True builds.

Fixes llvm#130112
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants