[uClibc]Re: uCLibc

Erik Andersen andersen at lineo.com
Wed Feb 7 20:29:06 UTC 2001


On Wed Feb 07, 2001 at 12:07:42PM +1100, AVENARD,JEAN-YVES (HP-Australia,ex2) wrote:
> Dear Erik
> 
> Hope you're doing fine.
> 
> I'm currently trying to compile uCLibc on a SH3 based platform running a
> linux kernel 2.4.0. On our device we are currently running short in space
> and I was thinking about using your uCLibc instead. Is there any
> restrictions to uCLibc, can it be used with normal linux or it has to run
> with uCLinux only.

No, it runs just fine with standard Linux kernels.  There are no restrictions
other then the constraints of the LGPL license (you can make closed source
apps, but if you do you must make available object files so folks could, in
theory, link against a different C library).

> All the documentation I've read so far mention only either ARM or M68K
> processor. Is there any architecture based component in ucLibc ? Looking in
> the source code it doesn't seem so. I see a 68k directory but the file
> contains ML only for the 68881 which has far as I know a FPU.

A couple of things.  First, make sure you are working with the
version from cvs.uclinux.org, which is where all current development
is going on.

There is some arch dependant stuff, in sysdeps/linux/<arch>.  To do
a sh port, look at what x86 does, and do the same things for sh.

> Is there a FAQ somewhere explaining how to use uclibc instead of glibc, link
> and cross-compiler etc ..
> 
> A lot of questions as you can see and I apologize in advance if it's been an
> inconvenience.

To use uClibc after compiling, the simplest way is the use the gcc wrapper
that is built in the final stage of the uClibc compile in extra/gcc-uClibc

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--





More information about the uClibc mailing list