On Wed, Aug 17, 2005 at 10:34:23AM +0200, Leif Adelw wrote: > Doing a forced install of the multisync rpm will result in a dynamic > linkage runtime error, i.e. the openobex libs are really different.
Have you tried installing the openobex RPM that I linked to in the previous mail? That is definitely the preferred option, as forcing the multisync RPM to install is unlikely to work. > This is also seen when compiling the 0.82-2 version - I get a linkage > error. Using multisync cvs code WORKS (using a common subset of > 1.0.so.0 and 1.0.so.1 openobex lib functions?) in the aspect that it > compiles and, as mensioned, I used it together with plugins from > 0.82-2 where evo2->backup synch was succesful. I don't know specifically what versions of multisync will work with different library versions, my only advice would be that when compiling from source you should use the latest available version of the library and its development package. This is because libraries are usually designed to be backwards compatible. > Perhaps the OBEX protocol is not used (or loaded) at this level? Do > you still think the problem with SE T630 and cable readout is related > to the OBEX lib? I'm not sure where the problem lies there. I can offer advice on installing multisync and its libraries, but the developers are the best ones to consult once multisync is running. Perhaps switching on debugging output will provide more information? -- Ruaidhri ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Multisync-users mailing list Multisync-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-users
