[uClibc]Todo & Thanks

[Shane Nay]

Supplemental question I forgot to ask.  What would it take to get uClibc to 
work happily along say libstdc++?, has anyone tried?  I'd rather just do 
without c++ code, I still have nasty headaches when I think about vtable 
initialization, but the other people I work with have already started in on 
me about it.  Is there any micro c++ library implementation that maybe 
excludes things like templates, and doesn't have any virtual functions 
internal to it that's out there?

Thanks,
Shane Nay.

> Okay, with that done, down to work.  I've finally convinced
> management/manufacturing that we need an MMU on that ARM chip, so we've
> targetted CLPS7212 as our target CPU.  (Does anyone know what the dev
> boards cost btw?, I'd rather buy my own because I hate giving them back
> when the project is over)  So, now with an ARM and a MMU, what work is
> there to do on uClibc to use it in a production enviroment?  Not
> necessarily specific to ARM, but just in the library itself?  Initially
> I'll be more focussed on just getting the dev boards and whole system up
> and running, but after that I'll have to loop back to help bring the system
> into place.  I realize that uClibc is probably not ready for a production
> system, so which areas need work to bring it to this level?, is there a
> list?  I'm happy to help in anyway that I can, and I have done quite a bit
> of work on glibc2.0.7 and some on gcc in the past, so I think I can help
> out.