Closed nix-enthusiast closed 2 months ago
Apologies for I couldn't provide the project code. It's too complex to send.
can you try a cargo clean and then rebuild, this looks like something was corrupted or a file was not read correctly.
can you try a cargo clean and then rebuild, this looks like something was corrupted or a file was not read correctly.
Now cross
command doesn't do anything, seems frozen. Both crates.io and git version behaves same.
Docker seems running and journalctl
doesn't report anything.
I moved my source code to a new project folder and it works as intended.
Problem solved.
Checklist
Describe your issue
I moved to Linux Mint 21.3 to Fedora 39 and installed
cross
inside a distrobox container (docker inside of distrobox is working without problems).Project used to be cross-compiled to given platforms but now none of my cross-compilation attempts were successful despite
Cargo.toml
and source files are same.Project can be compiled in host target (
x86_64-unknown-linux-gnu
,i686-unknown-linux-gnu
)What target(s) are you cross-compiling for?
aarch64-linux-android, aarch64-unknown-linux-gnu, aarch64-unknown-linux-musl, aarch64-unknown-freebsd, i686-linux-android, i686-pc-windows-gnu, i686-unknown-freebsd, x86_64-linux-android, x86_64-pc-windows-gnu, x86_64-unknown-freebsd, x86_64-unknown-linux-musl, x86_64-unknown-netbsd
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5 (35be2a9 2024-04-06)
Example
Output
Cargo.toml
Additional information / notes
I didn't provide results of all targets I tried because they throw as same error as the error I give it in example.