Skip to content
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

Many problems on RPI3 and Batocera #351

Open
erichlf opened this issue May 19, 2024 · 0 comments
Open

Many problems on RPI3 and Batocera #351

erichlf opened this issue May 19, 2024 · 0 comments

Comments

@erichlf
Copy link

erichlf commented May 19, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant