here's a dumb cvs question you might know the answer to.. When I was using the main branch (HEAD) of logjam cvs, I could do a 'cvs diff -r logjam_3_1' to find the differences between the main branch and the new one. Now that I've updated to the logjam_3_1 branch, I want to view the differences between that and the main, but 'cvs diff -r HEAD' doesn't produce the desired results. Any ideas?

er nevermind, I kinda got it.. cvs rdiff does something close to what i want.

What's the command line you're using? I don't know how to do it. :)

(Note that there have been a lot of changes, though mostly small things.)

cvs rdiff -r HEAD -r logjam_3_1

I'm kind of annoyed that I can't do it with cvs diff though.. When I specify -r HEAD [-r logjam_3_1], it doesn't show any differences. Maybe HEAD just means the head of the branch, not the head of the entire tree.. If so, there's probably another keyword I'm missing somewhere.

cvs rdiff -r HEAD -r logjam_3_1 logjam
(notice the module name at the end)

cvs diff -r logjam_3_0_2
works for me...

Go into the src/ directory, and give me the output of
"cvs status init.c"

That's the problem, I can specify a certain tag, but not the difference between the current main trunk and the current logjam_3_1 tree when my logjam directory is set to the logjam_3_1 tag.

===================================================================
File: init.c Status: Up-to-date

Working revision: 1.4.2.1
Repository revision: 1.4.2.1 /home/cvslj/logjam/src/init.c,v
Sticky Tag: logjam_3_1 (branch: 1.4.2)
Sticky Date: (none)
Sticky Options: (none)

Oh, I see, like a forward diff.

The sticky tag there indicates you're using the branch.

I think you'll have to do it *from* the head tree and do a diff against the 3.1 branch:
cvs co logjam
(no -r parameter means it won't get the branch)
cd logjam
cvs diff -r logjam_3_1

But that has the diff in the wrong way; logjam_3_1 is the newer version.

Er, I just confused myself.

yeah, the spec file is really wrong. i'll email the correct one (i wasn't using the one in the tarball) to you tomorrow morning, as well as making fresh rpms.

What version of libxml are you using? I'm getting a compile error:

conf_xml.c: In function `conf_xml_write':
conf_xml.c:390: structure has no member named `root'

Found the answer already ... you'll need to use xmlDocGetRootElement, I'm not sure if that's libxml2 specific, if it is I'm sure it should be easy enough to grab some code to do the same thing.

I see the read code already does that ...

OK, quick patch is at http://www.netcomuk.co.uk/~billc/logjam-xmlfix.patch

Hey, I just noticed the same thing-- I was using libxml1 and I should be using libxml2.

Give me a bit.
I'm porting to GTK 2.0 and a *lot* has changed. :)

OK ;o)

Are you willing to take patches for bugfixes, or should I wait until things settle down a bit?

Give me a few days.

Especially for GTK2, there's a lot of stuff that needs to be fixed, so patches will be very welcome.

One vital one then (escaped so you can cut'n'paste and feed into patch -p1 in the top directory :):

diff --recursive --unified logjam-logjam_3_1/src/network.c logjam-local/src/network.c
--- logjam-logjam_3_1/src/network.c     Mon Jan  7 04:02:09 2002
+++ logjam-local/src/network.c  Mon Jan  7 04:02:20 2002
@@ -25,6 +25,7 @@
 #include <curl/curl.h>
 #include <pthread.h>
 
+#include "config.h"
 #include "protocol.h"
 #include "util.h"
 #include "conf.h"

Hi, I'm trying to compile logjam 3.0.2 on an SGI O2 workstation running IRIX 6.5.14. I'm using gcc 3.0.1, but I've also tried the SGI compilers without success.

I ran configure with the --with-gnome=no option, and doing --with-xmms=no doesn't change anything.

This comment is too long with the errors included, so I threw them up on a temporary webpage. Click <A HREF="http://home.cwru.edu/~bjf10/logjamerrors.html>here</A> to see them. Thoughts? Thanks, Brian.

The warnings related to libnsl seem to be a well-documented problem with configure. I'll have to read more to figure that out.

I was helping someone else with the halfgnome errors. I seem to be doing something that isn't portable.

I'll look into this tonight.

Any progress? I greatly appreciate the effort.

Ages ago I got loserjabber 2.1.5 to compile correctly on this machine, with xmms but no gnome support. I recall running into a similar problem with the compiling, but solved it rather quickly. Unfortunately I didn't document my work at all... alas.

on my slackware8 box I get this on clicking 'login':

bash-2.05$ logjam
Can't open '/home/matt/.logjam/rc' -- will create.
Can't open '/home/matt/.logjam/moods' -- will create.
Segmentation fault

it'll briefly open the network connection little window thing, then die. it also dies in the same place when given a l/p on the cmd line. tcpdump shows nothing's going out

this happens from 3.0.2 source, rpms, cvs, 3_1 cvs

any ideas?

Can you give me a backtrace?

From the LogJam directory:
ulimit -c 10000
(makes it produce core files)
./logjam
(wait for it to segfault)
gdb ./logjam core
(should load this up, hit enter until you get a prompt)
bt
(should give you a list of functions)

And then paste that into an email to evan@livejournal.com.


Thanks...

I also get the segfault. RedHat 7.2...

I had to (obviously) install the gdb debugger and instead of gdb ./logjam core, I had to use gdb ./logjam core.PID , PID being the process ID that LogJam had when it SegFaulted... It may be blatantly obvious, but Ive never dumped cores or backtraced before, so this took me a while to get working O;-)