Open Multirious opened 1 year ago
Update:
I've done a wsl --unregister debian
.
and got a new, fresh, and hot Debian.
I've done:
Installed Rust first through this default installer and proceed default installation.
sudo apt-get -y update; sudo apt-get -y upgrade
sudo apt-get -y install curl
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source "$HOME/.cargo/env"
and then something along these lines:
sudo apt-get -y install podman build-essential
cargo install cross
then test the thing
cargo init --bin hello
cd hello
cross run --target aarch64-unknown-linux-gnu
And it has been working just fine! I don't know what happen in the first configuration I've got.
Update 2: I've reconfigured my new Debian with my personal dotfiles repository, which mean the corrupted Debian and this Debian should have about the same configs.
I've tested cross just for my current system. It went just fine. What actually went wrong?
I've tested cross for x86_64-pc-windows-gnu
.
Boom.
My terminal is now all f*cked up. Luckily didn't crashes this time.
My tmux key binds stop functioning for a minute.
My helix editor on the left side of my tmux pane just straight up gone and giving me bell notification on every key presses.
Executing any commands now give SEGV
apparently?
zsh is some how is still functioning, including the plugins.
I executed exec zsh
in my last effort.
It returns
zsh: locking failed for /home/peach/.config/zsh/zsh_history: read-only file system
Does anyone have any idea before I have to go test every single config?
Cross doesnt do anything magical with WSL, it simply invokes podman or docker.
You can see what happens with -v
added to the command.
I don't think this is a cross issue, it should go to wsl I think.
Checklist
Describe your issue
Update: Apparently it's configuration issue(?). Since I've done created a new Debian installation and it went fine. I don't know what went wrong with my first config.
I'm on Window 10, WSL2 Debian 12.
I was going through Getting Started tutorial section. I installed
podman
with the default configuration. After I rancross run --target aarch64-unknown-linux-gnu
, it crashes my WSL and literally corrupted it.Here's the terminal log:
What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
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
Example
Following Getting Started tutorial on Windows 10, WSL 2 Debian 12.
And bye bye my Debian. Anyways, the Debian is not that important. I was just testing around.
Additional information / notes
I'm on zsh shell with some long configurations.
podman
uses default configuration. I have changedtarget-dir
forcargo
.