Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 5 and Version 6 of FAQssl


Ignore:
Timestamp:
May 23, 2007, 3:18:43 PM (17 years ago)
Author:
John Bailey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQssl

    v5 v6  
    140140The notes below on installing GNUTLS as non-root may also be helpful, even if not exactly what you want.
    141141
     142=== Non-root Including Mozilla NSS and NSPR ===
     143Download the NSS and NSPR [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_9_2_RTM/src/nss-3.9.2.tar.gz source] and extract it.  Then do:
     144{{{
     145~$ cd nss-3.9.2/mozilla/security/nss
     146nss-3.9.2/mozilla/security/nss$ make nss_build_all
     147nss-3.9.2/mozilla/security/nss$ make install
     148}}}
     149
     150The Mozilla build system defaults to using the OS-supplied cc even if it's not in the path.  If you're compiling on Solaris (and possibly other Unixes), you'll need to force the build to use gcc using the following commands instead:
     151{{{
     152nss-3.9.2/mozilla/security/nss$ NS_USE_GCC=1 make nss_build_all
     153nss-3.9.2/mozilla/security/nss$ NS_USE_GCC=1 make install
     154}}}
     155
     156On systems where make is not GNU make, use gmake.  The above commands will build the libraries without optimizations and with debugging enabled.  To build optimized libraries, use these commands instead:
     157{{{
     158nss-3.9.2/mozilla/security/nss$ make BUILD_OPT=1 nss_build_all
     159nss-3.9.2/mozilla/security/nss$ make BUILD_OPT=1 install
     160}}}
     161
     162To install the libraries and necessary headers, do the commands in the following block, but note that they require GNU find and GNU cp.  These GNU tools can be found on Sunfreeware.com in the findutils and coreutils packages, respectively.  Remember to make sure either that the GNU utilities are in your path before the OS versions or that you explicitly give the full path to the GNU utilities for all of the commands below.
     163{{{
     164nss-3.9.2/mozilla/security/nss$ mkdir -p $HOME/lib
     165nss-3.9.2/mozilla/security/nss$ mkdir -p $HOME/include/nspr
     166nss-3.9.2/mozilla/security/nss$ find ../../dist/*/lib -type l \
     167> \( -name "*.so" -o -name "*.chk" \) \
     168> -exec cp -L {} $HOME/lib \;
     169nss-3.9.2/mozilla/security/nss$ cp -Lr ../../dist/public/* $HOME/include
     170nss-3.9.2/mozilla/security/nss$ cp -Lr ../../dist/*/include/* $HOME/include/nspr
     171}}}
     172
     173Now, to compile Pidgin, do the following after downloading and extracting the source:
     174{{{
     175~/pidgin$ ./configure --prefix=$HOME --with-nss-includes=$HOME/include/nss \
     176> --with-nspr-includes=$HOME/include/nspr --with-nss-libs=$HOME/lib \
     177> --with-nspr-libs=$HOME/lib
     178~/pidgin$ make
     179~/pidgin$ make install
     180}}}
     181
     182After the above, you should be able to use Pidgin by running `$HOME/bin/pidgin`.  In some cases it may be necessary to set `LD_LIBRARY_PATH=$HOME/lib` before running Pidgin.
     183
    142184== Random Questions ==
    143185
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!