-
Notifications
You must be signed in to change notification settings - Fork 377
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: linker i686-w64-mingw32-gcc
not found
#758
Comments
Can you provide the output of |
If I install cross from git, the following works fine: $ cargo install cross --git https://github.com/cross-rs/cross
$ git clone https://github.com/cross-rs/rust-cpp-hello-word
$ cd rust-cpp-hello-word
$ cross run --target i686-pc-windows-gnu
Compiling cc v1.0.73
Compiling hellopp v0.1.0 (/project)
Finished dev [unoptimized + debuginfo] target(s) in 42.90s
Running `wine /target/i686-pc-windows-gnu/debug/hellopp.exe`
0044:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0044:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0044:err:systray:initialize_systray Could not create tray window
Hello, world! So everything seems to work if using the latest versions. |
|
Yeah that means you're using the very old version installed from crates.io, which has some major bugs we're fixing in a new release. For a while, we had a lack of maintainers, so we've been patching some errors that had built up over time. If you reinstall cross from git (as shown above), this should fix your issue. You can always use a specific commit if you'd like to lock version dependencies. For example, to use the currently latest commit, and ensure you've audited the correct version, use: cargo install --git https://github.com/cross-rs/cross --rev 6a7fa09d6307acb5380475b134ff749c7cd9ed35 This will also warn you if any commands fall back to the host: cross --version
cross 0.2.1 (6a7fa09 2022-06-05)
Warning: Falling back to `cargo` on the host.
cargo 1.61.0 (a028ae42f 2022-04-29) Thanks for your patience with the lack of recent releases, due to the lack of maintainers. |
It feels like it isn't running in Docker?
The text was updated successfully, but these errors were encountered: