Instalation in 005-ps2sdk.sh fails

[fjtrujy]

Hello guys,
I have been installing from the scratch everything regarding the PS2Dev because I have formatted the computer.

So far I have noticed that the ps2toolchain is not working on the script 005-ps2sdk.sh.

So basically the issue is that the PS2SDK, looks to not work building with more than one processor.
So the issue it-self is not on the toolchain, maybe is on the PS2SDK.

I'm using a MAC on High Sierra 10.13.6 and the output of sysctl -n hw.ncpu returns 8

If I force to do it with a single processor instead of 8, the compilation works without problem.

Not sure if I should open the issue on the PS2SDK, but so far, there on the documentation they didn't mention anything to compile it using several processor, that why I have opened the issue here.

Thanks in advance

[sp193]

On my end, I do not know what we should do. I always thought it wasn't working and hence is not done, which was why my update to the CPU core detection parts did not cover this script.

It is a a Make thing. If it doesn't work, then there is something about our scripts that is not complete, but I do not know what.
I guess most of us don't own a Mac either, so could you please provide the error message?

[sp193]

Also, maybe @uyjulian can help share some insights on this, if he has worked with Makefiles on Mac before.

If it requires a complicated rework to the PS2SDK's Makefiles, I think it is okay to remove the -j option. I have no better solutions for this issue.

[uyjulian]

There is a dependency issue, and I have a solution for that. Instead of running separate make jobs for each subdirectory, just run one make job and use the include directive for each directory.
It will be in my cleanup7 branch. I might or might not rollup EE/DVP intrinsics into that branch.

[fjtrujy]

Hello guys!!
Thanks for your support. As I said this is not a blocker at all because just removing. the -j option, makes everything work again.

I just raised the issue in order to make it clear and not forget it.

More than happy if @uyjulian has already a solution in his branch.
If you really need testing I can help as well, just to try in a different computer.

Thanks again

[sp193]

This is currently worked around in 78deb4d, by unsetting PROC_NR.