I've got gaim-encryption compiled and installed on debian - no probs.
Now for freebsd - has anyone successfully compiled? - i've hacked away at the configure script (2.08/2.10/cvs) yet still no luck..
If you've had any luck can you give me some pointers please - gaim-encryption is only any use if both parties are using the plugin :-)
I've compiled it on BSD. The two tricks are:
1) get the location of the NSS/NSPR libs nailed down
2) set the LIBS variable on the call to configure, to add -pthread:
If your NSS install is sufficiently strange (it doesn't seem like any two Linux distros do it the same way, much less different unices), you may need to add other custom changes to the ./configure command line. For example, suppose that your nss headers are in /usr/include/nss/, except that they can't find another header file that is in /usr/krb5/include. Well, you can use:
LIBS=-pthread INCLUDES="-I/usr/krb5/include" ./configure
should do the trick, since the configure script should auto-detect the nss headers in /usr/include/nss. If your nss headers were somewhere else, you could tack on the --with-nss-includes="..." option.
If you can suggest an easy way to detect whether -pthread can/should be added to LIBS in the configure script, please let me know.
I installed 0.71 and encrypt 2.15 fairly easily.. using the port and then editing the configure for 2.15 .. their are a couple lines about nspr that need changed.
I do have a problem though, when i enable encrypt and it tries to generate keys, it just hangs forever.
My guess is that it is hanging when trying to get entropy for key generation. Two things to try:
Run gaim from the command line with -d. You should see some messages from the plugin when it gets loaded, and it will hopefully show where it hangs.
Move your mouse around a bunch when it is hung- that will give it more entropy.
The plugin _should_ have a pop-up window on the screen when it is generating keys, but GTK seems a little fickle about actually drawing it sometimes (for example on Windows).
" their are a couple lines about nspr that need changed" - which lines? can you paste me a diff ? i hacked around with configure but got nowhere..
in the new releases i didn't have to change those configure lines
however, im still having the freezing up problem... i enable the plugin and it says generating keys and then just sits there for a 'very' long time
gaim -d doesn't reveal anything unusual either
btw: what i did to install (after i cvsup my ports tree)
1. cd /usr/ports/net/gaim && make build && make install
2. download gaim-encryption-2.18 and unpack it into /usr/ports/net/gaim/work/gaim-0.73/plugins
3. cd /usr/ports/net/gaim/work/gaim-0.73/plugins/gaim-encryption-2.18
4. ./configure --prefix=/usr/X11R6 --with-nspr-includes=/usr/local/include/nspr --with-nspr-libs=/usr/local/lib --with-nss-libs=/usr/local/lib --with-nss-includes=/usr/local/include/nss/nss
&& make && make install
(but like i said it hangs when i enable the plugin, like it is currently)
My guess is that it is hanging in the call to PK11_GenerateKeyPair, file rsa_nss.c, line 237.
Without a BSD machine here to test on, I'm pretty stuck. I don't know whether it is a bug in NSS on BSD, or in the way the plugin is using it. I'll see if I can find a BSD box around here to debug on.
damnit, I cant get it to work either...
I have gaim 0.74 installed from ports and nspr-4.3_2 nss-3.8 installed from ports... heres what I get..
[root@beast]# ./configure --prefix=/usr/local --with-nspr-includes=/usr/local/include/nspr --with-nspr-libs=/usr/local/lib --with-nss-libs=/usr/local/lib --with-nss-includes=/usr/local/include/nss/nss
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking build system type... i386-unknown-freebsd4.9
checking host system type... i386-unknown-freebsd4.9
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for gaim header files... ../../src
checking for Mozilla nspr4 includes in /usr/local/include/nspr...
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking nspr.h usability... yes
checking nspr.h presence... yes
checking for nspr.h... yes
checking prio.h usability... yes
checking prio.h presence... yes
checking for prio.h... yes
checking again for Mozilla nspr4 includes in /usr/local/include/nspr... yes
checking for Mozilla nspr libraries... no
checking for Mozilla nspr4 libraries... no
configure: error: Error trying to link against the NSPR libraries.
Make sure to specify --with-nspr-libs="dir"
where "dir" is the location of the NSPR library file,
probably libnspr4.so or libnspr4.a
[root@beast]# ls -al /usr/local/lib/libns*
-rw-r--r-- 1 root wheel 292938 Oct 9 23:50 /usr/local/lib/libnspr4.a
lrwxrwxrwx 1 root wheel 13 Dec 26 12:46 /usr/local/lib/libnspr4.so -> libnspr4.so.1
-rwxr-xr-x 1 root wheel 226420 Oct 9 23:50 /usr/local/lib/libnspr4.so.1
lrwxrwxrwx 1 root wheel 12 Dec 26 12:46 /usr/local/lib/libnss3.so -> libnss3.so.1
-r-xr-xr-x 1 root wheel 464604 Oct 10 00:03 /usr/local/lib/libnss3.so.1
lrwxrwxrwx 1 root wheel 15 Dec 26 12:46 /usr/local/lib/libnssckbi.so -> libnssckbi.so.1
-r-xr-xr-x 1 root wheel 193060 Oct 10 00:03 /usr/local/lib/libnssckbi.so.1
so whats wrong with that? ;)
Log in to post a comment.