4 ms·

Congrats on the release! How standalone are the standalone executables produced by `bun build`? Is a libc or equivalent expected to be present?

• Jarred 3y ago
  Bun does need glibc, but older glibc versions should work okay because of this: https://github.com/oven-sh/bun/blob/78229da76048e72aa4d92516e296a57484450a30/src/bun.js/bindings/workaround-missing-symbols.cpp#L27 https://github.com/oven-sh/bun/blob/78229da76048e72aa4d92516... We haven't implemented polyfills for everything yet though, like Bun uses posix_spawn and doesn't have an exec + fork fallback Bun's dependencies otherwise are statically linked
  • codethief 3y ago
    > Bun does need glibc Wait, are we talking about what Bun needs to run or what standalone executables produced by bun build need in order to run?
    • hiccuphippo 3y ago
      Both, the executables produced by bun are the bun binary concatenated to your script at the end. Try building a hello world and run `tail -c200 hello | xxd` to see your script at the end of the file.
      • codethief 3y ago
        Thanks!
  • 10000truths 3y ago
    Is there any plan to allow for statically linking with musl to get completely shared-lib-dependency-free executables?