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. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgppYaFz3U00M.pgp
Description: PGP signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
