Michael Dusan

[EDIT: changed my mind on this, I don't think these concerns matter, hiding comment] re: a Zig "detection method", it's not clear to me how to avoid partial result-location updates...

i threw in these 2 statements and could it be @typeOf() strips away `constant` which is why it seems to work ``` diff --git a/std/rand.zig b/std/rand.zig index 654d1e5b..3ad45cd6 100644 ---...

This issue appears to manifest with stage2 **but not** with stage1. To be clear I am not sure this is a bug, it could just be that stage2 inlines better...

for posterity OP's .zig source can be found here: [owzu.zip](https://github.com/ziglang/zig/files/9795073/owzu.zip)

this looks related to #14111 short story: not an issue specific to freebsd; it's probably happening on all *unix platforms My memory is a bit fuzzy, but I think I...

related: andrew just opened #19352 How about this pattern, makes the test gate relatively simple: ```zig const native_os = @import("builtin").os.tag; // suggest put this in lib/std/c.zig between // `pub const...

> So now only the second mystery remains. yeesh. It looks like libc (at least on archlinux, x86_64) doesn't define strong symbols. #### (output trimmed) ```sh nm -D /usr/lib/libc.so.6 |...

have you tried cmake options: ``` -DZIG_STATIC_ZLIB=ON -DZIG_STATIC_ZSTD=ON ```

I like this. It's always irked me that we have things like `src/musl.zig` that has sort of poor-mans build logic when the build system already exists.

build native. For that you may use `zig cc` but do not set any env like CC or CXX. Workout any problems with a hello.c program. Difficult to guess why...