>> Actually, given your description of the problem, I'm half inclined
>> to revert the whole patch and instead make configure's test for
>> availability of <netinet/tcp.h> first include <netinet/in.h>, so
>> that that configure test will succeed on IRIX etc.
Pete, After looking at this I'm confused again. The configure test
consists of seeing whether cpp will process
#include <netinet/tcp.h>
without complaint. I can well believe that the full C compilation
process will generate errors if <netinet/tcp.h> is included without
also including <netinet/in.h>, but it's a little harder to believe
that cpp alone will complain. Could you double-check this?
It would be useful to look at the config.log file generated by the
configure run that's reporting tcp.h isn't found. It should contain
the error messages generated by failed tests.
regards, tom lane