Skip to content

wasmtime-jit fails to built when compiled standalone #200

@marmistrz

Description

@marmistrz

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions