-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing stdbool.h on cargo build
#41
Comments
I found the problem. Because the header file ends in |
kubkon
added a commit
that referenced
this issue
Nov 7, 2019
…ndows (#41) * Move path_get outside of sys module * Add implementation of readlinkat * Clean up path_open; use OpenOptions as much as possible * Enable close_preopen test * Implement path_create_directory; fix path_open * Refactor path concatenation onto a descriptor * Implement path_remove_directory * Implement path_unlink_file * Rewrite path_open using specific access mask * Fix error mapping when unlinking file * Fix readlinkat to pass nofollow_errors testcase * Clean up winerror to WASI conversion * Spoof creating dangling symlinks on windows (hacky!) * Add positive testcase for readlink * Implement path_readlink (for nonzero buffers for now) * Clean up * Add Symlink struct immitating *nix symlink * Fix path_readlink * Augment interesting_paths testcase with trailing slashes example * Encapsulate path_get return value as PathGet struct * Remove dangling symlink emulation * Extract dangling symlinks into its own testcase This way, we can re-enable nofollow_errors testcase on Windows also. * Return __WASI_ENOTCAPABLE if user lacks perms to symlink
kubkon
pushed a commit
to kubkon/wasmtime
that referenced
this issue
Mar 11, 2020
…lliance#41) * add a lifetime to the wiggle_runtime::GuestErrorType trait, wiggle_tests::WasiCtx struct * wiggle-generate: make config parsing public so it can be reused in lucet
grishasobol
pushed a commit
to grishasobol/wasmtime
that referenced
this issue
Nov 29, 2021
These limits seems to be picked arbitrary, and I just made it arbitrary larger. We need to reconsider these limits, ideally providing to user a way to customize the limits. FWIW, When the last time I've tried to run gcc's torture testsuite with wasmi it also bumped into this limit. Fixes bytecodealliance#41.
frank-emrich
added a commit
to frank-emrich/wasmtime
that referenced
this issue
Jul 11, 2023
This patch implements the `cont.bind` operator.
dhil
added a commit
to dhil/wasmtime
that referenced
this issue
Nov 3, 2023
Weekly merge with upstream
mooori
pushed a commit
to mooori/wasmtime
that referenced
this issue
Dec 20, 2023
A missing newline caused the markdown to not be generated properly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error message:
The text was updated successfully, but these errors were encountered: