[uClibc]Re: How to make a v850(e)-elf cross compiler from the gcc3.2-uclibc-toolchain

Miles Bader miles at lsi.nec.co.jp
Wed Dec 11 05:10:21 UTC 2002


Anders Boegild <sredna at mip.sdu.dk> writes:
> I would like to make standalone c programs for the v850(e)-elf target ( 
> not running uClinux or anything ) and be able to #include<math.h> and 
> #include<stdio.h> ..etc.

uClibc is a typical runtime library in that it expects there to be a
kernel to do things like I/O -- e.g., if you do `printf', the C library
will use the `write' system call to do the actual output -- and it
sounds like you're describing a platform where you have no kernel at
all.  [and currently the only kernel supported by uClibc is linux.]

Do you have _any_ framework that will load your programs, provide system
services, etc., or are you expecting to put your program image into ROM
and have it run on the bare metal?  If the latter, you need to be a lot
more careful, and will probably have to do all the various low-level
platform-specific stuff yourself (though uClibc may provide a good
starting point).

Some alternatives you might want to consider:

  * newlib -- I really don't know much about this, but it comes with gcc
    (I think you need to just give --with-newlib to gcc's configure),
    supports the v850 to some degree, and my impression is that it's
    more targetted at `bare metal' applications than uClibc.
    [is there anyone out there that knows more?]

  * uClinux -- provides all the services that uClibc needs, though of
    course it needs a lot of memory itself (probably 1MB ROM / 2MB RAM
    is sufficient)

Of course no matter what you choose, you'll probably have to do some
platform-specific customization yourself.  What platform are you using,
incidentally?  Is it something you built yourself?

Cheers,

-Miles
-- 
I'd rather be consing.



More information about the uClibc mailing list