[Nestedvm] Planing a large C to Java migration project

[Louis Santillan]

What about musl or maybe dietlibc? (
http://www.etalabs.net/compare_libcs.html)

-L

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