status of 0.9.30 release

Bernhard Reutner-Fischer rep.dot.nop at gmail.com
Thu Sep 25 21:53:24 UTC 2008


On Mon, Sep 08, 2008 at 04:49:54AM +0200, Stefan de Konink wrote:
>Bernhard Reutner-Fischer schreef:
>> On Sun, Sep 07, 2008 at 09:56:13AM +0200, Carmelo Amoroso wrote:
>>
>>> Indeed I've few pending patches to push that may be worth
>>> including in .30 release.

I plan to roll an -rc2 during the weekend of the 4th october, fwiw.
An -rc1 is in uclibc.org/downloads/, the REVISION file contains the
revision the tarball was created at. There were some improvements since
then, so i recommend trying trunk instead.

>>> - locale supports fixes

I have touched the make machinery in extra/locale a bit to make it work
better for me, fwiw. I don't need locale, so tested fixes and
improvements are of course very welcome.

>>> - an optimized sh4 memcpy implementation (currently used
>>>   since a long time in uclibc-nptl, glibc and kernel)
>>> - getdents

what the issue with getdents?

>> - cleanup the libm problem. Either remove the problematic powerpc bits
>>   or get written permission from Apple so
>>   that "(C) Apple. All rights reserved" can be fixed to state that it's
>>   actually BSD or LGPL or PD. We should not postpone to fix that up, the
>>   0.9.30 release should not be shipped with this problem, imho.
>>   Since i don't need those powerpc bits, i suggest they should be
>>   removed now. If somebody complains then she should submit a fixed
>>   version.

done.

I have an additional patch pending that i will apply after a bit of testing:
http://uclibc.org/~aldot/uClibc/math-foo.00a.patch (respun, in case you
already had a previous version)
>
>- cris(v32) architecture needs updates:
>  - native string handling doesn't compile anymore due to memcpy/memset
>    (examples can be found from newlibc)
>  - crti.S need to be update specifically for CRISV32, patch already on
>    the mailinglist, newlibc made this distinction too.
>
>
>I have attemped to fix the first issue, but I have an issue with:
>__GI_memcpy & __GI_memset.

what's the problem? Perhaps we can help?

cheers,
Bernhard



More information about the uClibc mailing list