Tristan Ross

I might have a solution, it just needs to be verified. You just need to append this to your `PrometheusDriver` configuration: ```ts { requestInterceptor: { onFulfilled: (cfg) => ({ ...cfg,...

Endian as an attribute alongside `callconv` is more appealing imo. `u32le`/`u32be`, `u16le`/`u16be`, and so on do look nice but I don't think would be as flexible. Endian as an attribute...

@expikr Then how would you denote native endianess?

I ran into this issue myself the other day by bootstrapping Zig and then building Zig with the bootstrapped zig but disabling LLVM. I was targeting `x86_64-uefi`.

> error: unknown target CPU 'x86-64' Well, that target isn't even listed in the list of valid CPU types.

@Rexicon226 seems to have hit Zig assuming `.s` being used for assembly but instead its being used for linker files. Probably some sort of "inclusion context" would have to be...

@chergert That certainly is interesting. This idea of mine came from when I was at SCALE/NixCon NA. Being able to pass the mesa driver through the host and to each...

> 2. create mesa drivers with only glibc as a dependency by statically linking everything and use them on the host and in flatpak; add a glibc flatpak extension to...

> Is it impossible to link LLVM statically or is this just not possible in the build system because no sane person would want the size of LLVM in their...

> Just on linking LLVM statically, it's possible Anything is possible but it's just a huge pain to link because the libraries become so big that it OOM's any of...