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
Currently, native_main is dynamically linked with libc. This is almost never an issue, except for musl users like me. Now, of course, I could just shut up and build my own executables, but, fortunately, static linkage is easy enough to propose universally:
This increases the size of the binary slightly: 484K -> 523K. It should also help with reproducibility (though I doubt there are currently issues with that).
My main reservation with proposing this is that I don't know what this does on systems that aren't Linux, e.g. macOS, where static linking is unsupported. I assume that Nim does not statically link in such cases instead of building a fragile executable.
The text was updated successfully, but these errors were encountered:
Huge +1 to either fixing this with static linking, or providing Musl builds that are detected in the install script. I ran the install script and was trying to figure out why on earth :native still failed - then I remembered, oh right, I'm on Void Musl. nimble build and copying the resulting executable over top of ~/.local/share/tridactyl/native_main, and otherwise making no changes after what all the installer script did, worked fine.
Currently,
native_main
is dynamically linked withlibc
. This is almost never an issue, except formusl
users like me. Now, of course, I could just shut up and build my own executables, but, fortunately, static linkage is easy enough to propose universally:This increases the size of the binary slightly: 484K -> 523K. It should also help with reproducibility (though I doubt there are currently issues with that).
My main reservation with proposing this is that I don't know what this does on systems that aren't Linux, e.g. macOS, where static linking is unsupported. I assume that Nim does not statically link in such cases instead of building a fragile executable.
The text was updated successfully, but these errors were encountered: