What about musl or maybe dietlibc? (<a href="http://www.etalabs.net/compare_libcs.html">http://www.etalabs.net/compare_libcs.html</a>)<br><br>-L<br><br>On Thursday, September 1, 2011, Brian Alliet <<a href="mailto:brian@brianweb.net">brian@brianweb.net</a>> wrote:<br>
> On Thu, Sep 01, 2011 at 09:07:27AM +0200, Bertram, Alexander wrote:<br>>> - Newlib is the biggest block. As Brian said, it's a subset of glibc and<br>>> nestedvm uses an older version which is even smaller. There is some<br>
>> functionality missing (iconv, threads) but also a lot of superficial<br>>> differences (like no stdint.h) that take time to paper over.<br>><br>> I knew newlib had some limitations, but I wasn't aware it was causing<br>
> this much trouble. I guess we were just lucky enough to have really<br>> clean, almost pure ANSI C software to work with, which ran without a<br>> hitch under newlib.<br>><br>> I suspect getting glibc running on NestedVM wouldn't be too difficult<br>
> for somebody familiar with the glibc codebase, but the last time I<br>> looked at it I was scared off. If I had it to do over again I'd<br>> probably pick up the libc from one of the BSDs and use that. They're<br>
> much more up to date, but still simple enough to be easily understood.<br>><br>> -Brian<br>><br>> _______________________________________________<br>> Nestedvm mailing list<br>> <a href="mailto:Nestedvm@lists.hcoop.net">Nestedvm@lists.hcoop.net</a><br>
> <a href="https://lists.hcoop.net/listinfo/nestedvm">https://lists.hcoop.net/listinfo/nestedvm</a><br>>