Hullo! I'm wondering what the expected behaviour of a libio-based app
is running under a stdio-based hurd.
I am building a native glibc and have reached the sunrpc stuff. IIRC,
we don't build this in a cross-build.
Just running rpcgen under GNU/Linux (After everything's installed) presents me with a
large list of command line options.
During the build (or rather, right after an error...) I ran:
/disk1/build.glibc/elf/ld.so.1 --library-path
/disk1/build.glibc:/disk1/build.glibc/mach:/disk1/build.glibc/hurd
/disk1/build.glibc/sunrpc/rpcgen
And it returns immediately.
I'm wondering if the fact that the Hurd that I'm running was built
with a stdio-based glibc would prevent a libio-based glibc from
outputting things to the console.
Now, I'm fairly certain the program is at least minimally capable of
running, because:
# /disk1/build.glibc/elf/ld.so.1 --library-path
/disk1/build.glibc:/disk1/build.glibc/mach:/disk1/build.glibc/hurd
/disk1/build.glibc/sunrpc/rpcgen -Y /usr/lib -c
/disk1/libc/sunrpc/rpcsvc/bootparam_prot.x -o
/disk1/build.glibc/sunrpc/xbootparam_prot.T
cpp0: output pipe has been closed
I'll play around with it some more. I suspect my fiancee won't mind
me playing on the computer all day, since it means the house is
getting cleaned while glibc compiles. ;)
Tks,
Jeff Bailey
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
