I have a new theory. Mainly since I haven't found the same problem anywhere else online.
I think that months ago I compiled syncevolution from source over the .deb that had previously been installed. When the .deb got updated, it updated most things but may not have overwritten the custom compiled (but older) libsynthesis (or some similar library). This led to problems until I compiled the newer version and killed the old libraries. Unless we see this problem recur, I think it'd be best to just chalk it up as a singular error on my part. Cheers, -martin On Fri, 2009-10-16 at 18:47 +0200, Patrick Ohly wrote: > On Fri, 2009-10-16 at 17:34 +0100, Martin Eckart wrote: > > > Can you compare whether different libs are used? Run > > > "ldd /usr/bin/syncevolution" and then "ldd" on your self-compiled > > > binary. Any relevant differences? > > > > > > > The self compiled returns 55 results and the binary only 31. That's the > > only real difference I can tell. > > We compile with --enable-evolution-compatibility. That avoids hard > dependencies on EDS libs, which are know to vary between platforms in > ways that rename the library without affecting SyncEvolution otherwise. > > > Curiously, since compiling the binary now works fine as well. > > The original binary? > > > This > > makes me think the compilation process overwrote/fixed one of the > > necessary libraries. This makes me think it might be libsynthesis.so.0 > > or libsmltk.so.0 since they were compiled at that time. > > So you compiled as root? Can you reinstall the syncevolution .deb and > check whether it still works? > > The relevant library for XML parsing is libsynthesis.so.0. It's the one > which calls libexpat. > _______________________________________________ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
