Re: libcurl problem.
On Tuesday 27 November 2018 21:20:16 Roberto C. Sánchez wrote:
> On Tue, Nov 27, 2018 at 03:51:47PM -0500, Gene Heskett wrote:
> > curl (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl3 (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl3-gnutls (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl4-gnutls-dev (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> >
> > I knew I'd been looking at the error, but I didn't think it was THAT
> > far back up the log. But an app I hadn't used in a coupler years,
> > refused to go get the docs for a new version, which made me back it
> > up to the previous version I was familiar with, also refused, I
> > thought I'd dig a little deeper.
> >
> > Abd the fix is?
>
> Can you try to launch the offending application from the terminal and
> post the complete error output?
>
> Regards,
>
Ton't take long, its name is DriveWire, writtem in java. It sets up a
very high baud rate serial connection to an old TRS-80 Color Computer3
over a usb2 to a 7 port usb hub in the basement, which has a custom
built adapter cable plugged into the coco's bit banger port, giving
the coco 32 additional channels of i/o that can be used as virtual
disk drives, virtual terminal screens into the coco from a pc's screen.
a midi player, and access in text modes, to any printer attached to
the pc. All at speeds of about half that of a floppy controller.
I fired it up, and sent it to show me the documentation from the
drivewire wiki pages. And this is the trace:
======================
ene@coyote:/CoCo$ ./dwstart
/CoCo/dw4directory
gene@coyote:/CoCo$ deleting old lockfile /var/lock/LCK..ttyUSB1
total 0
drwxr-xr-x 2 www-data root 40 Nov 19 20:20 apache2
-rw-rw-rw- 1 root root 0 Nov 19 20:20 tdekbdledsync-:0.lock
total 0
drwxr-xr-x 2 www-data root 40 Nov 19 20:20 apache2
-rw-rw-rw- 1 root root 0 Nov 19 20:20 tdekbdledsync-:0.lock
27 Nov 2018 22:00:34 INFO [dwserver-9 ] DriveWire Server v4.3.3o starting
Warning: NineServer port already in use. Is another DW4UI running?
/usr/bin/x-www-browser: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or
directory
===========================
At that point I exited the app. The NineServer port message has been
there for years, thru at least a dozen new versions and has never
been a problem. At that point it had not yet drawn its gui, taking
another 3 or 4 secs to complete that. At that point I opened the help
pulldown and ask to see the docs from te wiki.
And thats is the complete trace, showing the libcurl.so.4 as not being loadable.
But its there:
ls -l /usr/lib/i386-linux-gnu/libcurl*
lrwxrwxrwx 1 root root 16 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.a -> libcurl-gnutls.a
-rw-r--r-- 1 root root 596234 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.a
-rw-r--r-- 1 root root 990 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.la
lrwxrwxrwx 1 root root 23 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.so -> libcurl-gnutls.so.4.2.0
lrwxrwxrwx 1 root root 19 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.so.3 -> libcurl-gnutls.so.4
lrwxrwxrwx 1 root root 23 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.2.0
-rw-r--r-- 1 root root 412384 May 16 2018 /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4.2.0
lrwxrwxrwx 1 root root 17 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.la -> libcurl-gnutls.la
lrwxrwxrwx 1 root root 17 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.so -> libcurl-gnutls.so
lrwxrwxrwx 1 root root 12 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.so.3 -> libcurl.so.4
lrwxrwxrwx 1 root root 16 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.so.4 -> libcurl.so.4.2.0
-rw-r--r-- 1 root root 433152 May 16 2018 /usr/lib/i386-linux-gnu/libcurl.so.4.2.0
Me not java expert except for drinking it. :-)
Doing a new ldconfig makes no difference.
Thanks Roberto C. Sánchez.
> -Roberto
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: