Hi,

I have some issues with getting a good tool chain which supports all the required header files. Here is what i have done till now...

Initially i had got tool chain from codesourcery but it didn't support all the required header files. Then with some difficulty, i was able to make my own tool chain. The result of this tool chain was "arm-elf" type. I tried to compile 2.6.30 and later versions using this tool chain but it errors out with the below error. I Googled but couldn't find much info on this.

ERROR: arch/arm/boot/compressed/misc.o uses VFP instructions

Second problem
Later on i got hold of "arm-linux" tool chain which was being used on a different project. With this i am able to compile the kernel and boot it successfully on the board but it crashes when loading "yaffs2" file system.

Third problem:

I wrote a hello world program, compiled "arm-linux" and flashed it on the board which was running Linux kernel compiled using "arm-eabi" tool chain. When i do ls, i am able to see my hello world program in the flash but when i try to execute ./hello, it says file not found.

Now i am confused as to how to get one tool chain which supports all header files and make things work.... can anyone please help me on this?

-Prashanth

Your development system must be completely consistent if you want to work with no pain.
You have to use the same arm-elf || arm-linux || arm-eabi compiler for kernel, filesystem tools and your hello world application.

A small contribution :
For my developpement I used : arm-none-eabi to compile the bootstrap.
And arm-none-linux to compile Uboot, linux and applications.

Regards.
Seb