Kerberos includes (was Re: [HACKERS] Port report: Fedora Core 3 x86_64)

2004-12-19 Thread Tom Lane
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 krb5.h I have here, that file is included by krb5.h; so both backend/libpq/auth.c and

Re: Kerberos includes (was Re: [HACKERS] Port report: Fedora Core 3 x86_64)

2004-12-19 Thread Andrew Dunstan
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 krb5.h I have here, that file is included by krb5.h; so both

Re: Kerberos includes (was Re: [HACKERS] Port report: Fedora Core 3 x86_64)

2004-12-19 Thread Tom Lane
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 8.0 - is it

Re: [HACKERS] Port report: Fedora Core 3 x86_64

2004-12-16 Thread Tom Lane
Bernd Helmle [EMAIL PROTECTED] writes: Peter Eisentraut [EMAIL PROTECTED] wrote: Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Instead of doing that, do: --with-includes=/usr/include/et This same workaround is in the RPMs. I wonder if it would be worthwhile for configure to

Re: [HACKERS] Port report: Fedora Core 3 x86_64

2004-12-13 Thread Peter Eisentraut
Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Instead of doing that, do: --with-includes=/usr/include/et This same workaround is in the RPMs. I wonder if it would be worthwhile for configure to assume the above when --with-krb5 is mentioned. I don't know how widespread this

Re: [HACKERS] Port report: Fedora Core 3 x86_64

2004-12-13 Thread Bernd Helmle
--On Montag, Dezember 13, 2004 17:23:06 +0100 Peter Eisentraut [EMAIL PROTECTED] wrote: Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Instead of doing that, do: --with-includes=/usr/include/et This same workaround is in the RPMs. I wonder if it would be worthwhile for configure

[HACKERS] Port report: Fedora Core 3 x86_64

2004-12-12 Thread John Gray
All went mainly well - but a couple of gotchas on the build (these may be Fedora bugs rather than PG ones). This install is pretty much brand new (2 days old) with very little local configuration, so should represent an FC3 out of the box. 1. com_err.h is in /usr/include/et/com_err.h and isn't

Re: [HACKERS] Port report: Fedora Core 3 x86_64

2004-12-12 Thread Andrew Dunstan
John Gray said: All went mainly well - but a couple of gotchas on the build (these may be Fedora bugs rather than PG ones). This install is pretty much brand new (2 days old) with very little local configuration, so should represent an FC3 out of the box. 1. com_err.h is in

Re: [HACKERS] Port report: Fedora Core 3 x86_64

2004-12-12 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] writes: Instead of doing that, do: --with-includes=/usr/include/et This same workaround is in the RPMs. I wonder if it would be worthwhile for configure to assume the above when --with-krb5 is mentioned. I don't know how widespread this particular file