Re: Glibc behaviour with libio

[Roland McGrath]

stdio/libio is just part of libc, and what's in libc has no direct effect
on anything except programs using that libc.  Aside from the danger of
accidentally installing new incompatible binaries in /lib, the only kind of
effect your libio-based programs have on the system is through the RPCs
they make.  It's certainly possible (and not even unlikely) that there are
bugs in libio on Hurd that make a libio-based program/libc send the wrong RPCs.

If you are doing the libio build, you need to start by doing a vanilla libc
build from the same sources and verifying first that each case works
properly in that build before concerning yourself with libio.

Once you have a good vanilla (i.e. old stdio) libc build, then do "make
check" and see what the results are.  Then you can do "make check" on the
libio build, and worry about those results before you deal with any other
cases of programs using the new libc (including things like rpcgen or zic
that are part of libc's build).