Ps2toolchain: Installation script fails

try
sudo apt-get -y install texinfo bison flex
If this solves your problem probably this dependencies should be checked before.

Thanks for helping me.
I tried to install bison and flex (texinfo was already installed) but sadly nothing changed: I get the same errors as before (I have some less warning tough).
Could it be that I'm missing some other dependecies?

Just wondering? In case it makes a difference, what versions (? --version) of these dependencies should we make sure we have?

@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.
In the end I managed to install the toolchain (as well as the other components of the development environment) using the ps2dev script as root, could it be a permission problem? (I know it doesn't seem to be so but I'm sure I don't have spaces or non latin characters in both the PS2DEV path and the username).

@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 git clone was made with root privileges, or any middle command by accident was made with root. In such cases, it is very difficult to track down where is "root". If you wish you can completely reinstall PS2DEV with user privileges with the provided solution.

@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