Hello all again! Some good news: With a gentle poking [1], the wasi-libc now have a tagged version(s) - or at least tags corresponding to the version used in a WASI-SDK. That should help us better agreement on which version to use down the road.
[1]: https://github.com/WebAssembly/wasi-libc/issues/317 Josh Stone <jist...@redhat.com> writes: > It might be fine to share this, as long as you are not patching upstream > wasi-libc in some weird way. Rust's use is pretty minimal from vanilla > sources, and mostly only updated when we need compatibility to build > with a new Clang, in wasi-libc's Makefile "check-symbols" target. I'm hoping we will be able to build it as-is; the only thing I'm now currently patching is the Makefile, so that it picks up CFLAGS from the environment. These flags get filtered to only those applicable to the wasm32-wasi target. The main issue I'm fighting with currently is the CC0-licensed dlmalloc and it's possible replacement with the musl one. It seems that the dlmalloc is used mainly because it does not need a mmap-like capabilities on the system; WebAssembly does not provide that. I'm yet to succesfully compile the libc with any other malloc implementation – any help or pointers appreciated. I've also opened an inquiry about this upstream [3]; we'll see how that goes. [3]: https://github.com/WebAssembly/wasi-libc/issues/319 -- Jan Staněk Software Engineer, Red Hat jsta...@redhat.com irc: jstanek
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
