-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
error[E0658]: imports can only refer to extern crate names passed with --extern
on stable channel
#165
Comments
switched to the |
You don’t need nightly to be able to build Wasmtime. However, looking at the info you submitted (thanks!), your Rust version might simply be too old. Wasmtime requires Rust stable version at least 1.32, while you were trying to compile with 1.31. Could you try updating your stable toolchain with |
kubkon
added a commit
that referenced
this issue
Nov 7, 2019
Since `wasmtime` now uses `wasi` and `wasi32` modules, we can now safely remove the `wasm32` module. This commit also updates `wasmtime` to the latest upstream.
pchickey
pushed a commit
to pchickey/wasmtime
that referenced
this issue
May 12, 2023
…alliance#165) Changing LLVM and/or Rust to avoid special handling of `main` is a fair amount of work, and there could be other toolchains with similar special rules for functions named `main`, so rename the command entrypoint back to `run`. We could potentially re-evaluate this in the future, such as in a preview3 timeframe, but for now, let's go with the simplest thing that works.
pchickey
added a commit
to pchickey/wasmtime
that referenced
this issue
May 12, 2023
* delete adapter src/main.o: this was accidentally left out of bytecodealliance#165 * move adapter, byte-array, and verify to a new workspace * rename byte-array crate to a name available on crates.io * add a readme for verify, also give it a slightly better name * CI: wit dep check in its own step, verify before publish, trim down publication * reactor-tests: delete deps symlinks * reactor-tests: manage wit with wit-deps * test: dont set default toolchain to nightly * wit-deps lock adapter * wit-deps lock reactor-tests wit-deps doesnt manage these for some reason
pchickey
pushed a commit
to pchickey/wasmtime
that referenced
this issue
May 16, 2023
…alliance#165) Changing LLVM and/or Rust to avoid special handling of `main` is a fair amount of work, and there could be other toolchains with similar special rules for functions named `main`, so rename the command entrypoint back to `run`. We could potentially re-evaluate this in the future, such as in a preview3 timeframe, but for now, let's go with the simplest thing that works.
pchickey
added a commit
to pchickey/wasmtime
that referenced
this issue
May 16, 2023
* delete adapter src/main.o: this was accidentally left out of bytecodealliance#165 * move adapter, byte-array, and verify to a new workspace * rename byte-array crate to a name available on crates.io * add a readme for verify, also give it a slightly better name * CI: wit dep check in its own step, verify before publish, trim down publication * reactor-tests: delete deps symlinks * reactor-tests: manage wit with wit-deps * test: dont set default toolchain to nightly * wit-deps lock adapter * wit-deps lock reactor-tests wit-deps doesnt manage these for some reason
dhil
added a commit
to dhil/wasmtime
that referenced
this issue
May 8, 2024
One of the previous merges inadvertently dropped support for certain operations on continuation tables. This patch is a quick fix to restore the functionality by interpreting continuation tables as func tables. Also, this PR imports the wasmfx-tools patch for subtyping check on `cont.new`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i can not seem to get
wasmtime
to build.as far as i can tell, I'm following the build instructions
details
cargo: cargo 1.31.0 (339d9f9c8 2018-11-16)
rustc: rustc 1.31.0 (abe02cefd 2018-12-04)
rustup: rustup 1.18.3 (435397f48 2019-05-22)
OS: Linux/Ubuntu 19+
the build fails with this error
The text was updated successfully, but these errors were encountered: