[Buildroot] uclibc vs glibc

[Charles Krinke]

Dear Khem:

I apologize for asking my question improperly. Let me try again.

Buildroot creates a roots with its internal toolchain, that is the one it
compiles as I understand it. With CodeSouecery, their web site for the none
buildroot now supports says it is glibc.

I am trying to understand how, from inspecting the .so files in /lib on the
target how to tell the difference. For instance, just concentrating on
libc.so.6, I can see the uclibc, generated by buildroot from its compile
toolchain that this is a softlink to libc-2.6.1.so and is 1.38mbytes. I can
also see that the libc.so.6 in a rootfa create by the CodeSourcey 2010.09
toolchain is a softlink to libc-2.11.1.so and is 1.49 mbytes, a little
larger. I think the 2.6.1 libc is uclibc and the 2.11.1 libc is glibc.

Can someone confirm that this is true? That is, that a rootfs built with
buildroot's internally compiled toolchain is uclibc, and that a roots built
with CodeSorcery's external toolchain in the latest release of buildroot is
indeed glibc.
On Apr 10, 2011 4:36 PM, "Khem Raj" <raj.khem at gmail.com> wrote:
> On (10/04/11 16:08), Charles Krinke wrote:
>> I have a quesiton on a different subject and that is the difference
between
>> uclibc and glibc from the MPC8323ERDB target viewpoint.
>>
>
> they are entirely different root file systems.
>
>> Here is what I think I know:
>> 1. The toolchain is independent of the notion of uclibc vs glibc.
>> 2. Several of the .so files in /lib on the target will be different
between
>> uclibc and glibc.
>> 3. An application needs to be compiled with the static (or dynamic)
>> libraries pertinent to glibc or uclibc with appropriate header files to
>> expect it to run on the target.
>>
>> Questions:
>> 1. Which .so files on the target are different? ld, libc, libstdc++ only,
or
>> others?
>> 2. Are the differing files on the target going to have the same names
behind
>> their softlinks
>> like ld.so.1->ld-2.11.1.so for instance?
>> 3. Can I configure the CodeSourcery toolchain to produce a rootfs with
>> either uclibc or glibc and if so, what might be some of the steps?
>
> Try using -muclibc or -mglibc options.
>>
>> --
>> Charles Krinke
>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
> --
> -Khem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110410/fe5cc0b3/attachment.html>