Upgrading Linux GCC on PS2 Linux

[Basic]

Hi I'm trying to upgrade gcc on the PS2 Linux distro.

I tried to upgrade to GCC3.3.1 but got errors relating to binutils stuff so I upgraded binutils 2.13.2 (I think 2.14 would have worked as well).

know when I try to configure the make file for the GCC I get an error telling me that my CC environment variable isn't a working compiler.

I did export CC="/usr/bin/gcc" just to be sure.

Has anybody experienced this? or know a work around.

[Mega Man]

The offical last version is:
Kernelloader - Browse /Sony Linux Toolkit/Package Update Files/gcc at SourceForge.net
Kernelloader - Browse /Sony Linux Toolkit/Package Update Files/binutils at SourceForge.net

I assume that you also have written this linux - Upgrading GCC from 2.9x - Stack Overflow or you have the same problem.

The R5900 CPU in the PS2 has a bug. There must be a minimum number of assembler instructions in a loop. The original Sony binutils are able to check this with a "warn short loops" parameter. The compiler uses this parameter for the assembler as default, because this is configured in the installed .spec file. I assume that you have overwritten the binutils binaries with a version without support for this parameter. So you need either to use a binutils version which supports this parameter or remove the parameter from the spec file. I would suggest to use gcc 3.0.3 and binutils 2.13.2 from the links above. Otherwise you will have many problems. For newer stuff you need to look at the Linux 2.6 thread in this forum (GCC 4).

[Basic]

Yep I wrote the Stackoverflow article as well. Thanks for those links I'll try them later today really hope this will work 2.95.2 is such a crap compiler

[Basic]

Ok i installed binutils mipsel, and src, dont quite know what todo with the .diff file.

installed the binary gcc, I get error messages for simple hello world program.

5008: Error: illegal operands `mult $2,$2,$3'
5046: Error: illegal operands `mult $2,$2,$3'

this is proberly down to my missed .diff file I guess.

[Mega Man]

The .diff doesn't fix this. There is still something wrong with the binutils. The assembler "as" should be able to compile a file with the text "mult $2,$2,$3". I think every version of MIPS binutils should be able to do it. You can use "strace -fF" to check which assembler is called. You can use parameter "-save-temps" with gcc to save the assembler files and use it directly with "as".

[Basic]

OK, just to make sure nothing is interfering, I did a clean install of the PS2 linux (this includes the sps2lib stuff)

I upgraded binutils, then tried to compile a simple hello world program.

prior to install

>as -v = 2.9-33-990721 (mipsEEel-linux) using BDF version 2.0-ee-990721

I downloaded the src.rpm for the binutils

>rpm --rebuild binutils.src.rpm
>rpm -i binutils.rpm --replacefiles

After upgrading binutils I tried to compile a simple c++ hello world program

> g++ -o fooWithBinutils2_13 foo.cpp -v

The error was

/usr/bin/ld: /tmp/ccJpc4xp.o: ISA mismatch (-mips2) with previous modules (-mips3)
Bad value: failed to merge target specific data of file /tmp/ccJpc4xp.o

The full output here

The output shows that the new version of as is being used

as -v -mwarn-short-loop -mcpu=r5900 -KPIC -mips2 -msingle-float -o /tmp/ccJpc4xp.o /tmp/ccQhpgC2.s
GNU assembler version 2.13.2.1 (mipsEEel-linux) using BFD version 2.13.2.1

Interestingly I can compile the file without link ok.

>g++ -c foo.cpp -v

full output here

But when I link it

>g++ -o foo foo.o -v

This results in the same error.
full output here

Thanks for your time on this. I feel frustrating close to this.

[Mega Man]

I think you need to use parameter "-mips2" or "-mips3" for g++. One of the parameters should work.

[Basic]

tried those -mips2 gives the same error, -mips3 different errors

"Error: illegal operands `lui'"

How would these updates be applied normally?

[Mega Man]

As far as I remember I installed gcc 3 without the new binutils on BlackRhino. I used the packages from deba5er.

I think the binutils are incompatible and you need to recompile all libraries. To prove this, try to compile the following package:
http://kernelloader.cvs.sourceforge....stic/?view=tar
This is a self contained program which needs no libraries. This will prove that the linker is working and the libraries are incompatible.