Andrew Sampson

> > I'm experiencing this issue even with .NET 8 > > That's not great. Could you share your setup or maybe even a minimal repro for us to take...

> We currently have quite a few things in the transitive build process which are "locked" to net8.0 and won't work with net9.0 and later... eg. > > [sentry-dotnet/src/Sentry/Platforms/Native/buildTransitive/Sentry.Native.targets](https://github.com/getsentry/sentry-dotnet/blob/61f90d663052feb1f1becd99eb44ad0e3892f27b/src/Sentry/Platforms/Native/buildTransitive/Sentry.Native.targets#L9-L15) >...

My pleasure. I did a quick test and modified the targets to accept NET8+ and it seemed to work fine.

> > [@Leont](https://github.com/Leont) Hoping the patches in https://github.com/6over3/zeroperl/tree/main/patches would get upstreamed, hintfile for WASM would get added to the stock perl, and it will get some smoke testing in CI......

Also, if supporting asynchronous WASI / WebAPI isn’t a priority, you could simplify things a bit. These articles might help clarify some of the trade-offs: https://andrews.substack.com/p/get-in-loser-were-rewinding-the-stack https://open.substack.com/pub/andrews/p/4-mains-or-nothing-at-all?utm_campaign=post&utm_medium=web Let me know...

I finally figured it out. Configure's locale format detection fails during cross-compilation, defaulting to name=value pairs. WASI uses positional notation with semicolon separators. Since Configure unconditionally overwrites hint file values,...

Let me know if I can provide any further details or funding for the sprint to help upstream & stabilize my work / findings. With [my latest batch](https://github.com/6over3/zeroperl/blob/main/stubs/zeroperl.c) of work...

I opened an issue [here](https://github.com/bytecodealliance/wasmtime/issues/8247).

I was looking at the workflows and it looks like builds are already produced for this triple? https://github.com/bytecodealliance/wasmtime/blob/d256e25065d339b922093c28333779a155a61ccb/.github/workflows/main.yml#L381

Thanks for this — I think the approach is right! However, I'm seeing build errors when testing the patch (without my sed replacement workaround). The issue is with `PERL_LC_ALL_SEPARATOR`: ```...