fsquillace / junest

The lightweight Arch Linux based distro that runs, without root privileges, on top of any other Linux distro.
GNU General Public License v3.0
2.08k stars 110 forks source link

Many problems on RPI3 and Batocera #351

Open erichlf opened 3 months ago

erichlf commented 3 months ago

I am trying to use JuNest on a Raspberry Pi 3 running batocera,

$ uname -a
Linux BATOCERA 6.1.73-v8 #1 SMP PREEMPT Fri Mar  1 05:01:42 Europe 2024 aarch64 GNU/Linux

After I run junest setup I don't seem to have $HOME/.junest/bin_wrappers. I do have $HOME/.junest/bin. Then if I run junest I get

/userdata/system/.local/share/junest/bin/junest: line 11: /userdata/system/.junest/bin/readlink: cannot execute: required file not found
/userdata/system/.local/share/junest/bin/junest: line 11: /userdata/system/.junest/bin/dirname: cannot execute: required file not found
/userdata/system/.local/share/junest/bin/junest: line 11: /userdata/system/.junest/bin/readlink: cannot execute: required file not found

When I log out and then log back in I run junest and then I get:

/userdata/system/.local/share/junest/lib/core/common.sh: line 103: getent: command not found
/userdata/system/.local/share/junest/lib/core/common.sh: line 103: getent: command not found
/userdata/system/.local/share/junest/lib/core/common.sh: line 103: getent: command not found

I tried running junest create-bin-wrappers but still didn't get a bin wrappers directory, but I also don't get the above error. In general, when I run a junest <command> I always get the above "command not found" error.

I've read these errors tend to be do to windows endline characters (funny I don't have windows), so I ran

find ~/.local/share/junest/ -name "*.sh" -exec dos2unix {} \;

and still got the same error. However, running junest -f seems to not result in these errors and everything works as expected. However, I was hoping to use the export PATH=$HOME/.junest/bin_wrappers:$PATH method.

After posting the uname I realized that someone had posted about no support for aarch64, so maybe this is related to #309?