On Sun, Apr 15, 2007 at 12:06:36PM -0500, Donn L Washburn wrote:
> I aalways install file in /usr/and not /usr/local. That is to
> guarntee that the older files are over written so no old files and old
> libs are not left around to confuse things. I correct any old links
> (OO is any example). I do let ldconfig take care of libs. include
> and manpages are placed in common places where SuSE put them.
I think that's a bad idea. Sometimes filenames change in newer versions
of packages, so the older files do not always get overwritten. Also, if
you overwrite files that belong to a package that is installed on your
system, your package manager may become confused; I hope you are at
least removing the distribution-supplied package before installing a
locally built one.
At any rate, if you are convinced that all the library dependencies are
installed correctly, I can only think of two things to try next. The
first is to shutdown jpilot, then rename your ~/.jpilot directory.
Start jpilot again and see if there is any improvement. If that works,
it is likely that one of your databases has become corrupted.
If that doesn't work, I would suggest using strace to help pinpoint
where the error is occurring.
Good luck,
Jason
P.S.
Why not use the SuSE jpilot and pilot-link packages?
--
Jason Day jasonday at
http://jasonday.home.att.net worldnet dot att dot net
"Of course I'm paranoid, everyone is trying to kill me."
-- Weyoun-6, Star Trek: Deep Space 9
More information about the jpilot mailing list