Skip to content
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

Closed
buckle2000 opened this issue Jan 12, 2019 · 1 comment
Closed

Missing stdbool.h on cargo build #41

buckle2000 opened this issue Jan 12, 2019 · 1 comment

Comments

@buckle2000
Copy link
Contributor

buckle2000 commented Jan 12, 2019

$ RUST_BACKTRACE=1 cargo build

Error message:

   Compiling wasmtime-runtime v0.1.0 (/tmp/wasmtime/lib/runtime)
error: failed to run custom build command for `wasmtime-runtime v0.1.0 (/tmp/wasmtime/lib/runtime)`
process didn't exit successfully: `/tmp/wasmtime/target/debug/build/wasmtime-runtime-d60ae619fe4012af/build-script-build` (exit code: 101)
--- stdout
running: "cmake" "/tmp/wasmtime/lib/runtime/signalhandlers" "-DCMAKE_INSTALL_PREFIX=/tmp/wasmtime/target/debug/build/wasmtime-runtime-e2adaa410bffafe9/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Debug"
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/wasmtime/target/debug/build/wasmtime-runtime-e2adaa410bffafe9/out/build
running: "cmake" "--build" "." "--target" "install" "--config" "Debug" "--"
[100%] Built target SignalHandlers
Install the project...
-- Install configuration: "Debug"
-- Up-to-date: /tmp/wasmtime/target/debug/build/wasmtime-runtime-e2adaa410bffafe9/out/./libSignalHandlers.a
cargo:root=/tmp/wasmtime/target/debug/build/wasmtime-runtime-e2adaa410bffafe9/out
cargo:rustc-link-search=native=/tmp/wasmtime/target/debug/build/wasmtime-runtime-e2adaa410bffafe9/out
cargo:rustc-link-lib=static=SignalHandlers

--- stderr
signalhandlers/SignalHandlers.h:7:10: fatal error: 'stdbool.h' file not found
signalhandlers/SignalHandlers.h:7:10: fatal error: 'stdbool.h' file not found, err: true
thread 'main' panicked at 'Unable to generate bindings: ()', src/libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
@buckle2000
Copy link
Contributor Author

buckle2000 commented Jan 12, 2019

I found the problem. Because the header file ends in .h, clang considers it as a C header.

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
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant