Closed ProgrammingCube closed 3 years ago
It looks to me as if this part of the makefile doesn't work: kernel: pigfx.img @if [ $(RPI) == 1 ]; then \ cp pigfx.img bin/kernel.img; \ elif [ $(RPI) == 2 ]; then \ cp pigfx.img bin/kernel7.img; \ elif [ $(RPI) == 3 ]; then \ cp pigfx.img bin/kernel8-32.img; \ else \ cp pigfx.img bin/recovery7l.img; \ fi;
But I have no idea why...
Funny enough, I did the same steps but on my home pc with windows 10, and it worked perfectly. So that's strange.
Compiling on Windows is completely different than on linux. The makefile isn't used at all on Windows. There's a batch file that handles compiling.
Interesting, my friend was able to compile on linux no problem. I tried downloading and compiling on my home pc, but the same error popped up. Is it possible its a toolchain issue?
EDIT I had my friend send me a copy of his Makefile, and wouldn't you know it, it worked. I am at a loss for words
I'm going to close this if you don't mind.
I think I have the arm cross compiler toolchain set up correctly, but I always seem to be "that guy" when setting up dev environments...
I got the uspi cloned into the right directory and there's no error from gcc, but I am getting these errors:
/bin/sh: 1: [: 4: unexpected error