Re: Re: T630+IrMC(cable)<=>Any - no connection

> On Tue, Aug 16, 2005 at 02:12:27PM +0200, Leif Adelw wrote:
>
> >> 1) Using fc3 rpm install of multisync-irmc-0.82-2.i386.rpm is not
> >> successful due to:
> >> ---
> >> error: Failed dependencies:
> >>         libopenobex-1.0.so.0 is needed by multisync-irmc-0.82-2.i386
> >> ---
> >> even if openobex-1.0.1-1.1.fc3.rf installed, providing
> >> ------
>
> ...
>
> >> I've tested linking:
> >> lrwxrwxrwx  1 root root    29 Aug  4 18:37 
> /usr/lib/libopenobex-1.0.so.0 ->
> >> /usr/lib/libopenobex-1.0.so.1
>
>
> This is just an RPM dependency problem.  You've two options:
>
> Install a version of openobex that provides libopenobex-1.0.so.0, like:
> http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/openobex-1.0.0-5.i386.rpm
> Because this is a FC2 RPM, that may cause dependency problems if
> something else depends on your current version of openobex.  Also, yum
> or up2date might try and automatically upgrade you to a different
> version - just be aware of that.  Your symlinking of the libraries
> didn't work because RPM doesn't look in /usr/lib for dependency
> information, it looks in the RPM database.
>
> If you can't do the above, then you could force RPM to install the
> package with the --force option, ignoring dependency problems.  However,
> this would probably break other applications, meaning you're much better
> off with the first solution.
>
Ruaidhri, thank you for your time and comment on rpm lib dep. database 
lookup - I wasn't aware of that! Doing a forced install of the multisync 
rpm will result in a dynamic linkage runtime error, i.e. the openobex 
libs are really different. 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. 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? 
Best Regards Leif




-------------------------------------------------------
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