Open serjflint opened 1 year ago
You can reproduce this with a basic hello world program in Rust. That should simplify tracking down the cause.
While I haven't tried with Zig directly for an equivalent Hello World program, at a glance it looks like Zig supports static builds just fine. (EDIT: zig build
vs zig cc
is a different story it seems)
It's more likely to be an incompatibility with how cargo-zigbuild
is implemented? libgcc
/ gcc_eh
are related to internals with the rust compiler or cargo
IIRC. Perhaps there is some logic there that needs to be carried over to cargo-zigbuild
🤷♂️
EDIT: I am partially wrong.
hello.c
with static linking (the advice there doesn't seem to apply to libc.a
as it'd compile but segfault when run on the same build host).cc
static build support before cargo-zigbuild
can do anything about it.
Zig Version
0.11.0
Steps to Reproduce and Observed Behavior
Hi! I am trying to statically cross-compile Ruff from Linux to Linux-ARM (aarch64-unknown-linux-gnu). At the linking stage with command
I get an error
I have config.toml like this:
The maintainer of cargo-zigbuild advised me to open an issue here https://github.com/rust-cross/cargo-zigbuild/discussions/186
Expected Behavior
Successful build as for Linux-x86_64