You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The compilation succeeds if cargo build is executed from the repository root, but fails if cargo build is executed from wasmtime-jit. Tested on Arch Linux, nightly. (feature(alloc) may not be used on stable)
$ cd wasmtime-jit
$ cargo build
...
Compiling wasmtime-environ v0.1.0 (/home/marcin/proj/wasmtime/wasmtime-environ)
error[E0432]: unresolved import `std::ops`
--> wasmtime-environ/src/compilation.rs:10:10
|
10 | use std::ops::Range;
| ^^^ help: a similar path exists: `rayon::std::ops`
warning: trait objects without an explicit `dyn` are deprecated
--> wasmtime-environ/src/cranelift.rs:92:51
|
92 | fn get_address_transform(context: &Context, isa: &isa::TargetIsa) -> Vec<InstructionAddressMap> {
| ^^^^^^^^^^^^^^ help: use `dyn`: `dyn isa::TargetIsa`
|
= note: #[warn(bare_trait_objects)] on by default
error[E0282]: type annotations needed
--> wasmtime-environ/src/compilation.rs:47:27
|
47 | body: buffer[range].to_vec(),
| ^^^^^^^^^^^^^ cannot infer type
|
= note: type must be known at this point
error: aborting due to 2 previous errors
Some errors have detailed explanations: E0282, E0432.
For more information about an error, try `rustc --explain E0282`.
error: Could not compile `wasmtime-environ`.
To learn more, run the command again with --verbose.
The text was updated successfully, but these errors were encountered:
* Fix compilation of wasmtime-environ from within wasmtime-jit.
Enable wasmtime-environ/std when wasmtime-jit's std feature is enabled.
Fixes#200.
* Fix wasmtime-debug build too.
mooori
added a commit
to mooori/wasmtime
that referenced
this issue
Feb 14, 2024
The compilation succeeds if
cargo build
is executed from the repository root, but fails ifcargo build
is executed fromwasmtime-jit
. Tested on Arch Linux, nightly. (feature(alloc)
may not be used on stable)The text was updated successfully, but these errors were encountered: