>Here is the output from config.log .. as you will see, there is an
>I/O [Error]. ...
Yikes! I see why you're having so much trouble.
>... which is why I need a pre-compilied binary to test.
I don't think we have any more 2.5.1 systems here. The security holes
caused us to upgrade everything to at least 2.6. I'll poke around a
bit but don't think it's very likely I'll find anything.
Sorry.
About the only other thing I can think of is to try to get gcc to behave
by putting another copy of /usr/include someplace else (do you have a
good copy?) and then doing something like this:
gcc -nostdinc -I- -I/usr/include.good ...
If you don't have a good /usr/include copy, I think I can find one on
an old system dump tape from here, if you want.
You might also try doing a dummy ufsdump to /dev/null to see if it is
going to be able to handle your scrozzled system. If it can't deal
with things either, it might be time to look at a complete restart of
some type (and yes, I understand this is a production machine for you --
I'm talking about a longer term plan).
> Steve
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
