Skip to content

Subsecond fails linking when using the wild linker #4158

@janhohenheim

Description

@janhohenheim

Problem

Using the wild linker results in the following error:

18:50:56 [dev] Failed to generate fat binary: Error: Failed to parse archive `/home/hhh/git/bevy_simple_subsecond_system/target/x86_64-unknown-linux-gnu/debug/examples/libfatdependencies-6bff08f7-06a4-5
Caused by:c56db67d134.a @ #1/8`
    Couldn't identify file type

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: libwild::file_kind::FileKind::identify_bytes
   2: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
   3: <alloc::vec::Vec<T,A> as alloc::vec::spec_extend::SpecExtend<T,I>>::spec_extend
   4: rayon::iter::plumbing::bridge_producer_consumer::helper
   5: rayon_core::join::join_context::{{closure}}
   6: rayon::iter::plumbing::bridge_producer_consumer::helper
   7: rayon_core::job::StackJob<L,F,R>::run_inline
   8: rayon_core::join::join_context::{{closure}}
   9: rayon::iter::plumbing::bridge_producer_consumer::helper
  10: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
  11: rayon_core::registry::WorkerThread::wait_until_cold
  12: rayon_core::join::join_context::{{closure}}
  13: rayon::iter::plumbing::bridge_producer_consumer::helper
  14: rayon_core::join::join_context::{{closure}}
  15: rayon::iter::plumbing::bridge_producer_consumer::helper
  16: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
  17: rayon_core::registry::WorkerThread::wait_until_cold
  18: rayon_core::registry::ThreadBuilder::run
  19: std::sys::backtrace::__rust_begin_short_backtrace
  20: core::ops::function::FnOnce::call_once{{vtable.shim}}
  21: std::sys::pal::unix::thread::Thread::new::thread_start
  22: start_thread
  23: __clone3
collect2: error: ld returned 255 exit status
18:50:56 [dev] Build completed successfully in 56081ms, launching app! 💫
18:50:56 [dev] Failed to open app: I/O Error: Permission denied (os error 13)

Steps To Reproduce

Steps to reproduce the behavior:

Expected behavior

The app to launch.
The problem is not with wild itself; running cargo build works.

Environment:

  • Dioxus version: dioxus 0.7.0-alpha.0 (48e925f)
  • Rust version: rustc 1.89.0-nightly (ce7e97f73 2025-05-11)
  • OS info: Fedora release 42 (Adams)
  • App platform: Desktop Linux

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions