Skip to content

Re-add libunwind to lldb-cmake-sanitized #703

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.

Sign up for GitHub

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

Jump to bottom
Merged
ndrewh merged 1 commit into from
Jan 14, 2026
Merged

Re-add libunwind to lldb-cmake-sanitized #703

ndrewh merged 1 commit into from
Jan 14, 2026

Conversation

@ndrewh
Copy link
Contributor

@ndrewh ndrewh commented Jan 14, 2026

After #702:

15:26:10  CMake Error at /Users/ec2-user/jenkins/workspace/llvm.org/lldb-cmake-sanitized/llvm-project/libcxxabi/CMakeLists.txt:57 (message):
15:26:10    LIBCXXABI_USE_LLVM_UNWINDER is set to ON, but libunwind is not specified in
15:26:10    LLVM_ENABLE_RUNTIMES.

@ndrewh ndrewh requested a review from Michael137 January 14, 2026 16:52
@ndrewh ndrewh merged commit 0fb1a9a into llvm:main Jan 14, 2026
4 checks passed
@ndrewh ndrewh mentioned this pull request Jan 14, 2026
Merged
ndrewh added a commit to ndrewh/llvm-zorg that referenced this pull request Jan 15, 2026
@ndrewh
Revert "Re-add libunwind to lldb-cmake-sanitized (llvm#703)"
933b540 
This reverts commit 0fb1a9a.
@ndrewh ndrewh mentioned this pull request Jan 15, 2026
Merged
ndrewh added a commit that referenced this pull request Jan 15, 2026
@ndrewh
Revert llvm-cmake-sanitized to not build libcxx, until a bootstrappin…
0c0326e 
…g build can be setup (#705)

Reverts #702, #703, #704 and 38fc3c3.

I think ultimately the solution will require something like #704, but it
needs some more work.

rdar://164487647
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Michael137 Michael137 Awaiting requested review from Michael137

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ndrewh