--On torsdag, augusti 04, 2005 20.54.55 +0200 Michael Nottebrock
<[EMAIL PROTECTED]> wrote:
On Thursday, 4. August 2005 19:38, Mikhail Teterin wrote:
The build of postgresql74-client automatically detects the Kerberos setup
and turns its use on.
Unfortunately, this causes postgresql-libpqxx's configure to fail:
configure:20852: cc -o conftest -O -pipe -march=pentium4
-I/opt/include -L/opt/lib conftest.c -lpq -L/opt/lib >&5
/opt/lib/libpq.so: undefined reference to `krb5_cc_get_principal'
/opt/lib/libpq.so: undefined reference to `krb5_sname_to_principal'
/opt/lib/libpq.so: undefined reference to `krb5_cc_default'
/opt/lib/libpq.so: undefined reference to `krb5_cc_close'
/opt/lib/libpq.so: undefined reference to `error_message'
/opt/lib/libpq.so: undefined reference to `krb5_free_error'
/opt/lib/libpq.so: undefined reference to `krb5_sendauth'
/opt/lib/libpq.so: undefined reference to `crypt'
/opt/lib/libpq.so: undefined reference to `krb5_free_principal'
/opt/lib/libpq.so: undefined reference to `krb5_unparse_name'
/opt/lib/libpq.so: undefined reference to `krb5_free_context'
/opt/lib/libpq.so: undefined reference to `krb5_init_context'
configure:20858: $? = 1
configure: failed program was:
I'd say, the postgresql74-client port should make sure, the kerberos libs
is linked into libpq, but I'm not sure.
This looks like a bug in the postgresql74-server port (masterport for
-client) to me: Kerberos support is supposedly controlled by OPTIONS
(and defaults to off), but the port does not take the necessary measures
to make sure kerberos support really gets disabled according to the
OPTIONS settings when configure detects its presence.
Hi,
I'm not sure this is correct. Here are the lines in pg's configure:
--
if test "${with_krb5+set}" = set; then
withval="$with_krb5"
case $withval in
yes)
krb5_prefix=/usr/athena
;;
no)
:
;;
*)
with_krb5=yes
krb5_prefix=$withval
;;
esac
else
with_krb5=no
fi;
--
So, if --with-krb is not set, with_krb5 is set to "no". Hence, I think the
port takes the necessary measures, namely by just not adding
--with-krb5=xxx. configure will not detect kerberos' precence unless
--with-krb5 is explicitally set.
That said, I get reports from ppl having problem with kerberos and
postgresql. I cannot reproduce the problems, but all problems have gone
away when turning the kerberos OPTION off.
Since I cannot reproduce these build errors, I'd like to know more about
your setup; FreeBSD version?
Also, what do you mean by:
The build of postgresql74-client automatically detects the Kerberos setup
and turns its use on.
I'm lost, what do you mean by "the Kerberos setup", and how does the port
automatically detect it?
Best regards,
Palle
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
