Tom Lane writes: > 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? I'm not quite sure whether it explains it, but note that preprocessor checks also "fail" when warnings are generated. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- [HACKERS] Re: Add support for <xti.h> Tom Lane
- Re: [HACKERS] Re: Add support for <xti.h> Bruce Momjian
- Re: [HACKERS] Re: Add support for <xti.h> Larry Rosenman
- [HACKERS] Re: Add support for <xti.h> Pete Forman
- [HACKERS] Re: Add support for <xti.h> Tom Lane
- [HACKERS] Re: Add support for <xti.h> Bruce Momjian
- [HACKERS] Re: Add support for <xti.h> Tom Lane
- Re: [HACKERS] Re: Add support for <xti.h&... Peter Eisentraut
- Re: [HACKERS] Re: Add support for <xti.h&... Pete Forman
- Re: [HACKERS] Re: Add support for <xt... Tom Lane
- Re: [HACKERS] Re: Add support for &... Tom Lane
- Re: [HACKERS] Re: Add support f... Pete Forman
- Re: [HACKERS] Re: Add suppo... Peter Eisentraut
- [HACKERS] Re: Add support for <xti.h> Pete Forman