Inclusion of toolchain forces static=on Go Targets to Dynamically Link

[zachcoleman]

The description pretty much says it all.

Maybe I don't know enough about this toolchain, but including it as a module and registering Zig toolchains has forced normally statically linked Go targets to become dynamically linked.

Before:

ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, for GNU/Linux 3.7.0, Go BuildID=redacted, BuildID[sha1]=a3055087e190f1087358decf3ff32c494c13fd58, stripped

After:

ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 2.0.0, Go BuildID=redacted, stripped

Using Bazel:

go_binary(
    name = ...,
    data = ...,
    embed = ...,
    static = "on",
    visibility = ["//visibility:public"],
)

Is there a way to maintain for other targets the correct behavior? This an only Go code target.

[zachcoleman]

Is this due to #171 ?

[zachcoleman]

Or is this a feature of Zig compiler itself that prevents the static linking of glibc (forcing good behavior).

rust-cross/cargo-zigbuild#231 (comment)