fix(libgvproxy-sys): force static linking of libresolv on Linux#382
Merged
DorianZheng merged 1 commit intomainfrom Mar 14, 2026
Merged
fix(libgvproxy-sys): force static linking of libresolv on Linux#382DorianZheng merged 1 commit intomainfrom
DorianZheng merged 1 commit intomainfrom
Conversation
Without this, `cargo:rustc-link-lib=resolv` links libresolv.so dynamically, defeating crt-static and producing a dynamically linked boxlite-shim binary that SIGSEGV on TLS access (fs:[0x28]) on some VMs. Force `static=resolv` on Linux and add explicit library search paths for both Debian/Ubuntu (/usr/lib/<triple>) and RHEL/manylinux (/usr/lib64) so the linker can find libresolv.a when building with --target.
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
1 participant
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.
Summary
static=resolvlinking on Linux to ensure boxlite-shim remains fully statically linked when built withcrt-static/usr/lib/<triple>) and RHEL/manylinux (/usr/lib64) so the linker findslibresolv.awhen building with--targetlibresolv.so(dynamic), producing a dynamically linked shim binary that SIGSEGV on TLS access (fs:[0x28]) on some VMsTest plan
fileconfirms statically linked,lddreports "not a dynamic executable"libgvproxy-sysinmanylinux_2_28_x86_64Docker container — resolv linked via/usr/lib64/libresolv.a