alexcrichton commented on issue #4533:
Could you double-check that this fixes at least the issue in #4523 (although I suspect more exist)
abrown commented on issue #4533:
Could you double-check that this fixes at least the issue in #4523 (although I suspect more exist)
Like compile with
cargo build --target aarch64-linux-android
or something else?
abrown commented on issue #4533:
Looks like something else is the problem now:
$ cargo build --release --target aarch64-linux-android ... error: failed to run custom build command for `psm v0.1.18` Caused by: process didn't exit successfully: `/home/abrown/Code/wasmtime/target/release/build/psm-d3851756418374a6/build-script-build` (exit status: 1) --- stdout OPT_LEVEL = Some("3") TARGET = Some("aarch64-linux-android") HOST = Some("x86_64-unknown-linux-gnu") CC_aarch64-linux-android = None CC_aarch64_linux_android = None TARGET_CC = None CC = None CFLAGS_aarch64-linux-android = None CFLAGS_aarch64_linux_android = None TARGET_CFLAGS = None CFLAGS = None CRATE_CC_NO_DEFAULTS = None DEBUG = Some("false") cargo:rustc-cfg=asm cargo:rustc-cfg=switchable_stack running: "aarch64-linux-android-clang" "-O3" "-DANDROID" "-ffunction-sections" "-fdata-sections" "-fPIC" "-Wall" "-Wextra" "-xassembler-with-cpp" "-DCFG_TARGET_OS_android" "-DCFG_TARGET_ARCH_aarch64" "-DCFG_TARGET_ENV_" "-o" "/home/abrown/Code/wasmtime/target/aarch64-linux-android/release/build/psm-975239bbdf5842b2/out/src/arch/aarch_aapcs64.o" "-c" "src/arch/aarch_aapcs64.s" --- stderr error occurred: Failed to find tool. Is `aarch64-linux-android-clang` installed?
alexcrichton commented on issue #4533:
Could you perhaps set
AR=true CC=true
and see how far the build goes? Given the error you got it's unlikely you even reached compiling ittapi-rs
abrown commented on issue #4533:
Could you perhaps set
AR=true CC=true
and see how far the build goes? Given the error you got it's unlikely you even reached compiling ittapi-rs$ AR=true CC=true cargo build --release --target aarch64-linux-android ... error: could not find native static library `psm_s`, perhaps an -L flag is missing? error: could not compile `psm` due to previous error
And, yeah, I do not see
ittapi
being built in the compiled crates up above that error.
abrown commented on issue #4533:
@gneworld, could you test out this branch to see if it resolves #4523 for you? I don't think I have the right system environment (toolchains, libraries, etc.) to check if indeed this commit will fix the build issue you found.
gneworld commented on issue #4533:
@gneworld, could you test out this branch to see if it resolves #4523 for you? I don't think I have the right system environment (toolchains, libraries, etc.) to check if indeed this commit will fix the build issue you found.
Compiling wasmtime-jit v0.40.0 (/home/mi/ext/minacore_mi11/mina_jit_aot/wasmtime/crates/jit)
error[E0433]: failed to resolve: use of undeclared crate or modulerustc_demangle
--> crates/jit/src/demangling.rs:7:28
|
7 | if let Ok(demangled) = rustc_demangle::try_demangle(name) {
| ^^^^^^^^^^^^^^ use of undeclared crate or modulerustc_demangle
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:270:5
|
270 | bincode::serialize_into(&mut bytes, &info)?;
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:421:21
|
421 | None => bincode::deserialize(section(ELF_WASMTIME_INFO)?)
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
cpp_demangle
--> crates/jit/src/demangling.rs:9:49
|
9 | } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
| ^^^^^^ not found incpp_demangle
|
help: consider importing one of these items
|
3 | use object::Symbol;
|
3 | use object::write::Symbol;
|
help: if you importSymbol
, refer to it directly
|
9 - } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
9 + } else if let Ok(demangled) = Symbol::new(name) {
|For more information about this error, try
rustc --explain E0433
.
error: could not compilewasmtime-jit
due to 4 previous errors
gneworld edited a comment on issue #4533:
@gneworld, could you test out this branch to see if it resolves #4523 for you? I don't think I have the right system environment (toolchains, libraries, etc.) to check if indeed this commit will fix the build issue you found.
@abrown unfortunately,
Compiling wasmtime-jit v0.40.0 (/home/mi/ext/minacore_mi11/mina_jit_aot/wasmtime/crates/jit)
error[E0433]: failed to resolve: use of undeclared crate or modulerustc_demangle
--> crates/jit/src/demangling.rs:7:28
|
7 | if let Ok(demangled) = rustc_demangle::try_demangle(name) {
| ^^^^^^^^^^^^^^ use of undeclared crate or modulerustc_demangle
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:270:5
|
270 | bincode::serialize_into(&mut bytes, &info)?;
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:421:21
|
421 | None => bincode::deserialize(section(ELF_WASMTIME_INFO)?)
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
cpp_demangle
--> crates/jit/src/demangling.rs:9:49
|
9 | } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
| ^^^^^^ not found incpp_demangle
|
help: consider importing one of these items
|
3 | use object::Symbol;
|
3 | use object::write::Symbol;
|
help: if you importSymbol
, refer to it directly
|
9 - } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
9 + } else if let Ok(demangled) = Symbol::new(name) {
|For more information about this error, try
rustc --explain E0433
.
error: could not compilewasmtime-jit
due to 4 previous errors
gneworld edited a comment on issue #4533:
@gneworld, could you test out this branch to see if it resolves #4523 for you? I don't think I have the right system environment (toolchains, libraries, etc.) to check if indeed this commit will fix the build issue you found.
@abrown unfortunately,
Compiling wasmtime-jit v0.40.0
error[E0433]: failed to resolve: use of undeclared crate or modulerustc_demangle
--> crates/jit/src/demangling.rs:7:28
|
7 | if let Ok(demangled) = rustc_demangle::try_demangle(name) {
| ^^^^^^^^^^^^^^ use of undeclared crate or modulerustc_demangle
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:270:5
|
270 | bincode::serialize_into(&mut bytes, &info)?;
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
bincode
--> crates/jit/src/instantiate.rs:421:21
|
421 | None => bincode::deserialize(section(ELF_WASMTIME_INFO)?)
| ^^^^^^^ use of undeclared crate or modulebincode
error[E0433]: failed to resolve: use of undeclared crate or module
cpp_demangle
--> crates/jit/src/demangling.rs:9:49
|
9 | } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
| ^^^^^^ not found incpp_demangle
|
help: consider importing one of these items
|
3 | use object::Symbol;
|
3 | use object::write::Symbol;
|
help: if you importSymbol
, refer to it directly
|
9 - } else if let Ok(demangled) = cpp_demangle::Symbol::new(name) {
9 + } else if let Ok(demangled) = Symbol::new(name) {
|For more information about this error, try
rustc --explain E0433
.
error: could not compilewasmtime-jit
due to 4 previous errors
Last updated: Nov 22 2024 at 16:03 UTC