In case there is anyone else out there using the ical calendar program
besides me, I thought I'd mention some steps I had to take to get it
to work with pilot-link 0.9.5.
(A further note: I'm using an old distribution of Linux -- Red Hat 6.1 --
so what I describe here may not occur with ``modern" distributions. But it
may save beginning users from a misstep or two.)
Installing the latest pilot-link worked just fine on my computer: my
thanks to David for that. However, when I compiled & ran syncal 0.8.6
(the latest version I could find), it complained that it could not find
libpisock. Running syncal with strace produced the following:
11730 open("/lib/i686/mmx/libpisock.so.4", O_RDONLY) = -1 ENOENT (No such file o
r directory)
11730 stat("/lib/i686/mmx", 0xbffff658) = -1 ENOENT (No such file or directory)
11730 open("/lib/i686/libpisock.so.4", O_RDONLY) = -1 ENOENT (No such file or di
rectory)
11730 stat("/lib/i686", 0xbffff658) = -1 ENOENT (No such file or directory)
11730 open("/lib/mmx/libpisock.so.4", O_RDONLY) = -1 ENOENT (No such file or dir
ectory)
11730 stat("/lib/mmx", 0xbffff658) = -1 ENOENT (No such file or directory)
which is odd, since neither directory ``/lib/i686" nor``/lib/mmx" exist on
my computer. Fortunately, I knew that this was due to ld.so.cache being
unable to find libpisock.so.4, & since pilot link puts libpisock.so.4 under
/usr/local/lib (which, FWIW, I think is the right thing to do), all it took
to fix this problem was to add /usr/local/lib to /etc/ld.so.conf, run ldconfig,
& syncal lept over that hurdle.
Next, however, was my attempt to run syncal from within ical. Syncal's
author supplies a tcl script to customize ical, which I installed per the
instructions. However, when I tried to invoke syncal from ical, I received
the following error message:
can't read "HOME": no such variable
while executing
"exec syncal -v $HOME/.syncal.log"
(procedure "pilot_sync" line 13)
invoked from within
This is an odd one, since $HOME properly expanded in the rxvt session I
launched ical from, & I would expect a bug where a tcl script read an
environment variable would have been caught & fixed long before I downloaded
syncal. No, I didn't play with coding -- I know very little about tcl. I
simply replaced ``$HOME" with the value for my home directory in the tcl
script, restarted ical, & everything worked fine.
The chief threat to syncal's usefulness appears to be the fact the latest
version of ical has fallen off the Internet with the disappearance of the
machine www.research.digital.com. Syncal's homepage points to what appears
to be an older version (2.0p2, vs. 2.2) of ical at MIT, but it would be
nice to know someone somewhere is keeping an eye on this bit of code &
the reason he hasn't touched it for a while is because there are no major
faults in it.
Geoff
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix
