openbsd-ports/databases/freetds/pkg
sthen c88475b046 update to freetds 0.91; add an openssl flavour (see README for details),
remove msdblib flavour (with @pkgpath to handle updates): this is not
really worth a separate flavour; just define MSDBLIB when building your
applications if you require this behaviour.
2011-09-08 17:13:51 +00:00
..
DESCR update to freetds 0.91; add an openssl flavour (see README for details), 2011-09-08 17:13:51 +00:00
PFRAG.shared - update to 0.82+patches 2009-08-01 14:11:19 +00:00
PLIST update to freetds 0.91; add an openssl flavour (see README for details), 2011-09-08 17:13:51 +00:00
README update to freetds 0.91; add an openssl flavour (see README for details), 2011-09-08 17:13:51 +00:00

$OpenBSD: README,v 1.1 2011/09/08 17:13:51 sthen Exp $

+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------

The main FreeTDS package uses GnuTLS if making an encrypted connection.
This requires thread support; due to limitations of OpenBSD's current
userland threads implementation, it is not always possible to load the
correct library automatically.

If you see errors like "undefined symbol 'pthread_mutex_unlock'" or
processes exiting when making a connection to an encrypted server, you
will need to manually load the pthread shared library; you can do this
by setting "LD_PRELOAD=/usr/lib/libpthread.so" in the environment.

Alternatively you may use the "openssl" flavor of the port; the licenses
of FreeTDS and OpenSSL are incompatible, therefore compiled packages may not
be distributed, so you will need to build this yourself.

Note that this does not apply for cleartext connections; the problem is
only seen when the encryption library is initialized.