Uh oh!
There was an error while loading. Please reload this page.
Make libunwind build hermetic - #72746
Conversation
rust-highfive
commented
May 29, 2020
(rust_highfive has picked a reviewer for you, use r? to override) |
petrhosek
commented
May 29, 2020
r? @tmandry |
rust-highfive
commented
May 29, 2020
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
We want to avoid exporting any symbols from Rust's version of libunwind, and to do so we need to disable visibility annotations to make sure that the -fvisibility=hidden has effect, and also hide global new/delete. This matches the CMake build of libunwind.
88eebff to
21abc88Comparetmandry
commented
May 29, 2020
@bors r+ rollup=never |
bors
commented
May 29, 2020
📌 Commit 21abc88 has been approved by |
Dylan-DPC-zz
commented
Jun 3, 2020
@bors p=1 |
jethrogb
commented
Jun 3, 2020
As asked previously, why don't you just use CMake to do the build? That avoids having to maintain a separate build flow. |
bors
commented
Jun 3, 2020
bors
commented
Jun 3, 2020
☀️ Test successful - checks-azure |
We want to avoid exporting any symbols from Rust's version of libunwind,
and to do so we need to disable visibility annotations to make sure that
the -fvisibility=hidden has effect, and also hide global new/delete.
This matches the CMake build of libunwind.