openbsd-ports

History

sthen 0dbcb43036 Drop separate OpenSSL flavour for FreeTDS. Change main package to using OpenSSL rather than GnuTLS. Permit packages to be distributed. Bump shared library versions to make sure they get updated. As researched by jasper@, the GPL has a special exception when something depends on software provided with the base OS, so it is ok for us to distribute this. This is preferred over using GnuTLS because GnuTLS pulls in a pthread dependency; pthread overrides libc functions, so it is necessary that a program using this is itself linked with pthread, causing a problem if you want to use the FreeTDS library to connect to servers using encryption from programs which aren't themselves linked with pthread (e.g. /usr/sbin/httpd with mod_php, or perl with DBD::Sybase). ok jasper@ ajacoutot@		2012-05-11 09:57:02 +00:00
..
DESCR	Drop separate OpenSSL flavour for FreeTDS. Change main package to using	2012-05-11 09:57:02 +00:00
PFRAG.shared	- update to 0.82+patches	2009-08-01 14:11:19 +00:00
PLIST	Drop separate OpenSSL flavour for FreeTDS. Change main package to using	2012-05-11 09:57:02 +00:00
README	update to freetds 0.91; add an openssl flavour (see README for details),	2011-09-08 17:13:51 +00:00

README

$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.