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
Installation script fails #72
Comments
try |
Thanks for helping me. |
Just wondering? In case it makes a difference, what versions ( |
@SignalSpectre it seems that you have some spaces or special characters in some path. This can be your PATH, (for example your username), PS2DEV, or something similar. Please ensure that your Windows username contains only Latin chars without spaces, and that you didn't change PS2DEV path into something with spaces or non-Latin chars, and that WSL username is also only Latin, and that your PC name is also only Latin. |
Both my Windows and WSL usernames are using only latin characters with no spaces and so is the PS2DEV path. |
@SignalSpectre It looks like permission problem, I just thought that you already tried to install it as root. I added a possible solution for this problem into Readme: export PS2DEV=/usr/local/ps2dev
sudo mkdir -p $PS2DEV
sudo chown -R $USER: $PS2DEV It is also possible that |
@rickgaiser @fjtrujy @SignalSpectre this issue can be closed - it was produced due to a permission denied problem which now is covered in Readme. |
Thank you for following up on this @AKuHAK |
I'm trying to install the toolchain on Windows Subsystem for Linux but I get these errors:
libtool: link: only absolute run-paths are allowed
make[3]: *** [Makefile:928: libbfd.la] Error 1
make[2]: *** [Makefile:942: all-recursive] Error 1
make[1]: *** [Makefile:1088: all-recursive-am] Error 2
make: *** [Makefile:1644: all-bfd] Error 2
../scripts/001-binutils-2.14.sh: Failed.
I really don't know how I can fix these (I tried searching the correct makefile but failed miserably…).
This happen to me every time even on different computers with a fresh installation of WSL: how can I solve it?
The text was updated successfully, but these errors were encountered: