DioxusLabs/dioxus · error · anyhow::Error

{} {}

Error message

{}
{}

What it means

Raised in run_link_inner (called from run) when the linker invocation or the surrounding link step produces two error payloads that are combined into a single bail with a `{}\n{}` format. This is the generic failure exit of the custom-linker path — where linker args were written to a file and an external linker was executed — so the message content comes from the linker/subprocess errors themselves rather than a specific guard.

Source

Thrown at packages/cli/src/cli/link.rs:159

        }

        // Write the linker args to a file for the main process to read
        // todo: we might need to encode these as escaped shell words in case newlines are passed
        std::fs::write(&self.link_args_file, args.join("\n"))?;

        // If there's a linker specified, we use that. Otherwise, we write a dummy object file to satisfy
        // any post-processing steps that rustc does.
        match self.linker {
            Some(linker) => {
                let mut cmd = std::process::Command::new(linker);
                match cfg!(target_os = "windows") {
                    true => cmd.arg(format!("@{}", &self.link_args_file.display())),
                    false => cmd.args(args),
                };
                let res = cmd.output().expect("Failed to run linker");

                if !res.status.success() {
                    bail!(
                        "{}\n{}",
                        String::from_utf8_lossy(&res.stdout),
                        String::from_utf8_lossy(&res.stderr)
                    );
                }
                if !res.stderr.is_empty() || !res.stdout.is_empty() {
                    // Write linker warnings to file so that the main process can read them.
                    _ = std::fs::create_dir_all(self.link_err_file.parent().unwrap());
                    _ = std::fs::write(
                        self.link_err_file,
                        format!(
                            "Linker warnings: {}\n{}",
                            String::from_utf8_lossy(&res.stdout),
                            String::from_utf8_lossy(&res.stderr)
                        ),
                    );
                }
            }

View on GitHub (pinned to 24f6a829df)

Solutions

1. The linker reported the two printed error lines. Read them and fix the underlying link problem.

When it happens

Trigger: Thrown at packages/cli/src/cli/link.rs:159 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23). Data as JSON: /api/errors/0aaf672884af5a7a. Report an issue: GitHub.