Sourcery G++ Lite Toolchain

[Franxis]

After seeing this thread in the pandora forums, i tried to use the Sourcery G++ Lite toolchain to compile executables for the WIZ:
http://www.gp32x.de/board/index.php?showtopic=46663

The toolchains are available here:
http://www.codesourcery.com/sgpp/lite/arm/...ubscription3057

The executables are compiled correctly, but after that when they are tested in the WIZ, they simple don't NOT run .

Only the oldest toolchain (Sourcery G++ Lite 2005Q1B) is running ok (but it is gcc v3.4 or so), the rest of the toolchains create executables not compatible with the Wiz. I don't know what's wrong... They targeted to ARMv5 linux soft-float. Compiling dynamically the error shown is "not found" and statically "illegal instruction".

Anybody knows what's the problem?

Regards.

 

[notaz]

Yes. There has recently been ABI change for ARM, there is now old ABI (OABI) and new ABI (EABI). See here:
CODE

http://wiki.debian.org/ArmEabiPort



Newer kernels and codesourcery toolchains use EABI. For some strange reason (backward compatibility?) Wiz chose to use OABI in it's kernel and libs, so it's doomed to use old toolchains unless they change that.

 

[Franxis]

Yes. There has recently been ABI change for ARM, there is now old ABI (OABI) and new ABI (EABI). See here:
CODE

http://wiki.debian.org/ArmEabiPort

Newer kernels and codesourcery toolchains use EABI. For some strange reason (backward compatibility?) Wiz chose to use OABI in it's kernel and libs, so it's doomed to use old toolchains unless they change that.


Thanks for the answer

 

[Exophase]

I do not know what GPH/AESOP/MES/whoever was thinking with going with OABI, but I never really know what they are thinking.

Can you use the new toolchain if you supply the GCC parameters for OABI?

EDIT: Contractions <_<

 

[notaz]

Not 100% sure but I think it's hardcoded in GCC

 

[Exophase]

Yeah, at first it looked like the link you provided was saying otherwise but the only thing that you can control here seems to be binutils.

 

[rahulgarg]

Just to follow up on the issue, has this been fixed? Is the newer (assuming there was a newer?) firmware using EABI or OABI?