On Sun, Aug 8, 2010 at 10:38 AM, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote: > In the long run (IMHO as soon as possible, actually), we should detain our > current BSD-libc-, glibc-, home-brewn-mess into a legacy folder (being used > with gcc2-haiku only) and then replace it with a current BSD-libc, extended > by our own specific additions. Otherwise, properly maintaining the POSIX > parts of our libroot is going to be virtually impossible. Good to hear that. I think it's a good direction for Haiku to use BSD libc. I would suggest to go even further and use the clang and http://libcxx.llvm.org/ instead of gcc4 and libstdc++. I've ported Haiku to use clang. It builds and works, but still uses some workarounds (especially for glibc parts in libroot.so). -- Grzegorz Dąbrowski (kaliber) http://tiltos.com http://home.gna.org/pingwinek/