You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed recently that compiling your libc example has different behavior on arm64 than it does on x86 -- on arm, it produces a static binary, but on x86 it's dynamically linked, even with CGO_ENABLED=0.
Is this intended? I initially observed similar behavior after using purego in another project, where my x86 go binaries broke because they switched from static to dynamic.
The text was updated successfully, but these errors were encountered:
I noticed recently that compiling your
libc
example has different behavior on arm64 than it does on x86 -- on arm, it produces a static binary, but on x86 it's dynamically linked, even withCGO_ENABLED=0
.Is this intended? I initially observed similar behavior after using
purego
in another project, where my x86 go binaries broke because they switched from static to dynamic.The text was updated successfully, but these errors were encountered: