ydoom wrote:
What I meant was, is it enough to compile GCC, or will I have to port newlib anyway?
It will definitely not be enough. I expect GCC to make use of several POSIX calls, whereas PDCLib is "only" C99 (so that it does not limit your design choices by making additional demands on the kind of system calls that you provide). That means that stuff like execve(), fchdir(), stat() etc. will need to be implemented
on top and
beside of PDCLib. Have a look at Rink Springer's
Ananas project. He has got dash, Lua and coreutils running on top of PDCLib plus POSIX extensions of his making, and is actively working towards getting binutils / GCC to compile on his OS. You might want to link up with him and combine efforts. I
might be interested in hosting a "PDCLib POSIX layer" somewhere down the line, and will certainly accept any sensible patches to PDCLib that might turn up during your endeavour (as I accepted Rink's patches). His code is beerware, by the way.
Edit: A quick sketch. PDCLib provides
only the "CLib" part (with the aforementioned limitations as it's not yet "released"), while keeping a minimal footprint. Newlib would give you POSIX, with more demands on your kernel, and a different licensing / upstream situation. It's your choice. PDCLib is mostly for those people who don't
want to support POSIX, or shun the available libraries for aesthetic reasons.