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

Thread 'main' panicked at 'called Result::unwrap() on an Err value: CrossCompilation' #124

Open
smartkrio opened this issue Jan 23, 2020 · 0 comments

Comments

@smartkrio
Copy link

Hello! Could you explain the nature of this bug? I can't find any info about that. So I try to build my app with cargo-raze and bazel. The trace below was given after try with fork, called ffmpeg4_sys, but I had the same result with any version of original library higher than 2.8.9.

ERROR: /home/skr/.cache/bazel/_bazel_skr/e43c6ea3a3e0071d84f6a78f03fdfca4/external/raze__ffmpeg4_sys__4_2_2/BUILD.bazel:54:1: Executing genrule @raze__ffmpeg4_sys__4_2_2//:ffmpeg4_sys_build_script_executor failed (Exit 101) thread 'main' panicked at 'called Result::unwrap()on anErr value: CrossCompilation', src/libcore/result.rs:997:5 stack backtrace: 0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39 1: std::sys_common::backtrace::_print at src/libstd/sys_common/backtrace.rs:71 2: std::panicking::default_hook::{{closure}} at src/libstd/sys_common/backtrace.rs:59 at src/libstd/panicking.rs:197 3: std::panicking::default_hook at src/libstd/panicking.rs:211 4: std::panicking::rust_panic_with_hook at src/libstd/panicking.rs:474 5: std::panicking::continue_panic_fmt at src/libstd/panicking.rs:381 6: rust_begin_unwind at src/libstd/panicking.rs:308 7: core::panicking::panic_fmt at src/libcore/panicking.rs:85 8: core::result::unwrap_failed 9: ffmpeg4_sys_build_script::main 10: std::rt::lang_start::{{closure}} 11: std::panicking::try::do_call at src/libstd/rt.rs:49 at src/libstd/panicking.rs:293 12: __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:87 13: std::rt::lang_start_internal at src/libstd/panicking.rs:272 at src/libstd/panic.rs:388 at src/libstd/rt.rs:48 14: main 15: __libc_start_main 16: _start Target //stalin/rtp_handler:server failed to build Use --verbose_failures to see the command lines of failed build steps. INFO: Elapsed time: 0.699s, Critical Path: 0.06s INFO: 0 processes. FAILED: Build did NOT complete successfully

Cargo toml with raze

[package]
name = "cargo_deps"
version = "1.0.0"
authors = ["Dmitrii <[email protected]>"]
edition = "2018"

[lib]
path = "fake_lib"

[dependencies]
ffmpeg4 = "0.4.0"


[raze]
workspace_path = "//third_party/cargo"
target = "x86_64-unknown-linux-gnu"
genmode = "Remote"

[raze.crates.ffmpeg4-sys.'4.2.2']
gen_buildrs = true

[raze.crates.clang-sys.'0.28.1']
gen_buildrs = true
skipped_deps = [
  "libloading-0.5.2"
]
additional_deps = [
  "@//third_party/cargo/overrides/libloading-0.5.2:libloading",
]

[raze.crates.env_logger.'0.6.2']
additional_flags = [
    "--cfg=atomic_cas"
]

[raze.crates.bindgen.'0.51.1']
gen_buildrs = true
extra_aliased_targets = ["cargo_bin_bindgen"]

[raze.crates.libloading.'0.5.2']
custom_build_file_path = "//bindgen/raze:libloading.BUILD"

[raze.crates.log.'0.4.8']
additional_flags = [
    "--cfg=atomic_cas"
]

[raze.crates.proc-macro2.'1.0.8']
additional_flags = [
    "--cfg=use_proc_macro",
]
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