##
## Executing the following command:
##
## { touch /usr/local/ps2dev/.test && rm /usr/local/ps2dev/.test; }
##
touch: cannot touch `/usr/local/ps2dev/.test': No such file or directory
I get this error while running the script with the command ./toolchain.pl PSP
Edit: I am running the normal shell script now, but I still wanted to know if I did something that got in the way of the Perl script properly running or being properly configured... maybe there is a hard coded directory... when the shell script is done rebuilding the whole toolchain and PSPSDK I will try to check out the Perl script itself, but I do not have high hopes to find the problem by myself if it is in the Perl script... I never really learned Perl so if it is not something obvious... well, I am a bit SOL on that one ;).
About the updated shell script: I see in the README of the perl script that it grabs the latest patches from SVN, was this functionality also included in the new shell script (you did say so in a post, but in that post you did not mention the fact that you had now prepared two versions of the script so I wonder if that comment was directed towards the new and improved shell script) ?
Specifically the "privs" line which tries to "touch" not existing files.
My question is this: if I am asking to build PSP files ( ./toolchain.pl PSP ) why does the script try to access files in a directory that should not matter to the program at all ( my $PS2DEV = "/usr/local/ps2dev"; ) ?
I will comment it and try to use it again (I think it should work just as fine as the other shell based script, I'll try to use it to update to the very latest PSPSDK posted in SVN since as you said this script goes looking in the SVN repository for the latest sources for PSPSDK, GCC, Binutils, Newlib, etc...).
Still, somethign wrong... I used option 6 which should say update and build the PSPSDK package only (and what about option 3 that mentions PSPSDK headers ? Should it be used along with this one ?), but the script is ignoring it and going from the 1st step forward.
Edit: minor correction, it starts downloading binutils... but then it kinda stops... (animated slash not moving for minutes).
That's also another bug - selecting single steps doesn't work.
When it finishes downloading the binutils source with wget, it uses svn to grab the latest patch from the pspdev subversion server. Unfortunately, the standard svn client will sit there and look frozen while it does its work... since there's no output, the spinner doesn't spin.
If you want to take a look at it, do a 'tail -f logfile.txt' in another window to see the progress.
Btw, the standard toolchain script still works as intended and will update you to the latest versions... there's no need to use the new toolchain script yet.
ooPo wrote:That's also another bug - selecting single steps doesn't work.
When it finishes downloading the binutils source with wget, it uses svn to grab the latest patch from the pspdev subversion server. Unfortunately, the standard svn client will sit there and look frozen while it does its work... since there's no output, the spinner doesn't spin.
If you want to take a look at it, do a 'tail -f logfile.txt' in another window to see the progress.
Oh I see, well that explain the single steps thing anf th "freezing" issue :).
Btw, the standard toolchain script still works as intended and will update you to the latest versions... there's no need to use the new toolchain script yet.
Of course there is, if no-one tests it what is the point of making it available :D?
One side story, you have told me so many times to run svn update with the shell script that now before running the latest shell script I do a svn update (which your script does on its own basically as it looks for the latest versions of everything... :)).