RE: [arm-gnu] Include path problem in CC-ing busybox

["James Kehl" <jamesk@xxxxxxxxxxx>]

> -----Original Message-----
> From: pavan_savoy@xxxxxxxxxxxxxx [mailto:pavan_savoy@xxxxxxxxxxxxxx]
> Sent: Tuesday, 12 August 2008 8:02 PM
> To: James Kehl
> Cc: arm-gnu@xxxxxxxxxxxxxxxx
> Subject: RE: [arm-gnu] Include path problem in CC-ing busybox
> 
> Thank you, very much, this made me look deep into arm-none-eabi vs. arm-
> none-linux-gnueabi.
> 
> So as a generic question If I want to CC a utility like this using a arm-
> none-eabi, then I would require all the underlying libs that a utility
> would require using a arm-none-eabi isnt it ?
> 
> Like in this case, I've have to have a glibC ?
> Please explain...
> 

It's not really a question of libc. It's a question of OS.

Are you going to run it under linux? Use arm-none-linux-gnueabi.

Are you going to run it under uClinux? Use arm-uclinuxeabi.

Are you going to run it under eCos? Hmmm... arm-none-eabi might work... but using the eCos toolchains would probably be easier.

Are you going to run it without an OS? Use arm-none-eabi, and remove the bits of busybox that depend on the OS - I don't think you'll have much left, though...
Are you going to write your own OS? Use arm-none-eabi, and... have fun.

James