Re: [issues] Why eglibc does not provide tarball?

[Gaye Abdoulaye Walsimou <walsimou@xxxxxxxxxxxx>]

Brett,
I totally agree with all you said. I just want to add some words.

Joseph,
I've worked, as embedded linux developer, in a company which designs MCU
based on MIPS core and they prefer using uClibc toolchain, because of
four things:
1- uClibc has buildroot
2- They can fix a version of uClibc (downloadable as tarball) in the
version of buildroot they deliver to their customers.
3- As this version of uClibc is fixed, all its bugs are know, they can
give advices (workaround) on these bugs and they do not follow a moving
target (with bugs they have to identify).
4- Their customers were happy with that.

They gave me these reasons when I've tried to tell them to use another C
library (because I thought uClibc lacks good nptl (priority inheritance,
etc.) ).
May be you will find that, with this strategy, this company is not the
kind of users that eglibc is intended ...

I've asked this question because I tried to estimate the amount of work
which is needed to create a tool like buildroot, but this time for eglibc.

cheers,