[uClibc]cross-compiled arm uclibc and gdb simulator

[Bjorn De Sutter]

Hi, 

on an i386 linux system, I've cross-compiled gcc and newlib as follows: 

../gcc-3.2.2/configure --prefix=/home/brdsutte/embedded/build-gcc --enable-target-optspace --with-newlib --target=arm-elf gmake all install

Then, I've build uClibc with CROSS=arm-elf- as follows:

make KERNEL_SOURCE=/home/brdsutte/embedded/linux TARGET_ARCH=arm 

The linux kernel I used for that compilation (i.e. who's headers are used during the
compilation of uClibc) was a standard linux 2.4.19, patched with
patch-2.4.19-rmk7 for the arm, and then configured for arm-integrator 

I then compiled gdb as follows:  

../gdb+dejagnu-20030417/configure--prefix=/home/brdsutte/embedded/build-gdb --target=arm-elf gmake all install

When I run a hello world program that I compiled with arm-elf-gcc using
arm-elf-gdb, everything works all right, but when I compile the same program
with arm-uclibc-gcc, trying to run the program results in the following: 

[brdsutte at elrond vb]$ arm-linux-run b.out 
sim: unknown SWI encountered - 900036 - ignoring 

One of the differences between the two version of the programs is that the 
newlib version only contains system calls swi 0x00123456, while the uClibc 
version contains system calls such as swi 0x00900001 

I've been told that there is no way to configure gdb in such a way that 
it understands the linux system calls in uclibc. Is there a way to 
configure uClibc in such a way that it uses arm-elf system calls, like 
the ones in newlib or the Arm Developer Suite generated code?

Please include my email address if you respond to this mail, as I am not 
subscribed to this mailing list.

Thanks in advance, 

Bjorn De Sutter
  Postdoctoral Fellow of the Fund for Scientific Research -- Flanders
  affiliated with Ghent University, currently at IBM TJ Watson Research Lab
  brdsutte at elis.ugent.be               http://www.elis.ugent.be/~brdsutte/