Changes between Version 18 and Version 19 of FAQssl

Timestamp:

Sep 15, 2009, 4:36:35 AM (14 years ago)

Author:

herrtodd

Comment:

Instructions on preventing the GnuTLS plugin from being used when NSS is specified at build time.

FAQssl

@@ -117 +117 @@
 > --with-nss-includes=$INCDIR --with-nss-libs=$LIBDIR
 }}}
+
+Prior to building Pidgin with NSS, remove the file `libpurple/plugins/ssl/ssl-gnutls.c` from the source tree to prevent the GnuTLS plugin from being built and used by Pidgin.
 
 If you can't add to `/etc/ld.so.conf` (or your *nix OS doesn't have one), set the environment variable `LD_LIBRARY_PATH` instead, either before running Pidgin or (for Bourne and bash shells) on the Pidgin command line, like so:
@@ -241 +243 @@
 If you've managed to build Pidgin with SSL support reported by `./configure` and no build failures, but when running it still complains, there are a few things you can try.
 
-Make sure that you only have one copy of Pidgin installed, it is possible that there is another one in your path that does not have SSL support. You can check which Pidgin is being run with "`which pidgin`", or you can be sure to run the version you've just compiled by specifiying the full path to it. Note: `./configure` will warn you if it finds an old version of Pidgin already installed.
+Make sure that you only have one copy of Pidgin installed, it is possible that there is another one in your path that does not have SSL support. You can check which Pidgin is being run with "`which pidgin`", or you can be sure to run the version you've just compiled by specifying the full path to it. Note: `./configure` will warn you if it finds an old version of Pidgin already installed.
 
 If you are sure that you are running your freshly compiled Pidgin, check Pidgin's SSL plugin is actually linked to the necessary libs. If you compiled with Mozilla NSS, you can do this (replace /usr/local with the prefix you installed to):