A few things have changed, but not much. Here's some hints:
1) If you get an error about -mcpu, just change it to -march.
2) Using -march seems to automatically specify a -mips level. Delete the offending -mips.
3) If you get errors about 'puts', add a -fno-builtin to your cflags.
I'm sure someone is going to come along and comment on how wrong I am and there's a better way to do it, to which I respond:
Why am I writing this message instead of you, hmm?
Hints on compiling using a gcc-3.x toolchain.
Hehe :-)
As for the -fno-builtin, maybe you would rather want to disable specific functions, like printf which will use puts which doesn't exist in the iop part. Depends on the amount of builtins to disable.
As for the -fno-builtin, maybe you would rather want to disable specific functions, like printf which will use puts which doesn't exist in the iop part. Depends on the amount of builtins to disable.
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.
Re: Hints on compiling using a gcc-3.x toolchain.
Doing a blanket -fno-builtin IMO is a bad idea. To fix puts() add -fno-builtin-printf. See the iop makefiles in ps2drv.ooPo wrote:A few things have changed, but not much. Here's some hints:
1) If you get an error about -mcpu, just change it to -march.
2) Using -march seems to automatically specify a -mips level. Delete the offending -mips.
3) If you get errors about 'puts', add a -fno-builtin to your cflags.
I'm sure someone is going to come along and comment on how wrong I am and there's a better way to do it, to which I respond:
Why am I writing this message instead of you, hmm?