-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
build: make libunwind linked dynamically #36697
Conversation
Off topic here, but linking libuv dynamically would likely fix #34627. Generally 👍 to dynamically linking more dependencies. 🙂 |
This is now dependent on us building libosxunwind.dylib correctly (JuliaLang/libosxunwind#16) |
040c196
to
104ba90
Compare
IIRC the problem was that we would pick up libosxunwind from libSystem. Do your build system tweaks fix that? Also, separate from this PR, but we should switch our upstream to the LLVM copy to pick up aarch64 support. |
Possibly—our dylib had accidentally just been an empty shell re-exporting libSystem. Can’t say it will work now, but definitely wouldn’t have worked before. And agreed we should attempt to apply our diff on top of a newer release. |
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically.
104ba90
to
76a6f64
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I'm happy to have more things used through a more regularized interface
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically.
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically. (cherry picked from commit 9267bbf)
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically. (cherry picked from commit 9267bbf)
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically. (cherry picked from commit 9267bbf)
Not sure why this was first linked statically, as the commit that introduced this simply had the message "restoring stuff that seems to have been clobbered by the revert of the unintended merge to master". Nearly all other libraries that we use are linked dynamically. (cherry picked from commit 9267bbf)
Not sure why this was first linked statically, as the commit that
introduced this simply had the message "restoring stuff that seems to
have been clobbered by the revert of the unintended merge to master".
Nearly all other libraries that we use are linked dynamically.