Steven Johnson

+1; my project has similar hard requirement and similar problem.

This is a pretty major problem for us, too. I'll try the genrule workaround suggested above, but it makes me mighty nervous.

Related to my previous comment: I have put together a utility script for myself that does the necessary hackery with with the .a files to produce a statically-linked output for...

> if a cc_library outputs at least some .pic.a library, I use them, otherwise I use all .a library Thanks, I'll give that a try. On the whole, Bazel is...

Eager to hear how this turns out -- it's one of the last sticking points for my project.

To be a little more clear: most of the failures are under WITH_WASI=ON, which has (eg) structs that aren't the sizes that are expected, e.g. `static_assert(sizeof(__wasi_fdstat_t) == 24, "witx calculated...

> Oh I assumed you had fixed this with #1628, sounds like there are a separate set of issues here? Correct (for #1628 I had not tried building on a...

From a casual inspection, it looks like the issue is just one of struct padding, eg `__wasi_fdstat_t` is basically `{ u8; u16; u64; u64; }`, which requires less padding on...

Yeah, this is puzzling; whatever tool generates this code makes some pretty specific assumptions about struct alignment and padding (apparently, that they always follow rules for x86-86, which seems odd)

> I think the layout is determined by that the wasm32 target produces (i.e. its a header mostly designed for code that is running in WebAssembly not the implementation side)....