"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> Tom Lane said:
>> Accordingly, I think we should just avoid the whole problem of exactly
>> where com_err.h lives by removing the #includes for it as well as the
>> configure test for it.
> Works for me. I'm not sure why the reasoning only applies to
Tom Lane said:
> I wrote:
>>> [ concerning a discussion about Kerberos' com_err.h being in
>>> /usr/include/et/ on some systems ]
>
>> Actually, I'm wondering why we directly include com_err.h at all. At
>> least in the version of I have here, that file is included by
>> krb5.h; so both backend
I wrote:
>> [ concerning a discussion about Kerberos' com_err.h being in
>> /usr/include/et/ on some systems ]
> Actually, I'm wondering why we directly include com_err.h at all. At
> least in the version of I have here, that file is included by
> krb5.h; so both backend/libpq/auth.c and inter
