WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: ntpdate refers to wrong library name  (Read 361 times)

Offline iwkse

  • Newbie
  • *
  • Posts: 8
ntpdate refers to wrong library name
« on: June 19, 2020, 01:55:08 PM »
Hi,
while executing ntpdate it does't start because libssl.so.1.0.0 and libcrypto.so.1.0.0 are not available.
Simlinking that to libssl.so and libcrypto.so let it run properly.

Regards

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 617
Re: ntpdate refers to wrong library name
« Reply #1 on: June 19, 2020, 07:39:04 PM »
What version of piCore are you running?  Version 11.x is using openssl 1.1.1

Offline iwkse

  • Newbie
  • *
  • Posts: 8
Re: ntpdate refers to wrong library name
« Reply #2 on: June 20, 2020, 12:54:05 AM »
Hi,

yes piCore 11.0 installed from here http://tinycorelinux.net/11.x/armv6/releases/RPi/

I've installed ntp from tce-ab

Code: [Select]
Title:          ntp.tcz
Description:    NTP utilities
Version:        4.2.8p7
Author:         Harlan Stenn
Original-site:  http://www.ntp.org
Copying-policy: Free, see COPYRIGHT
Size:           676k
Extension_by:   bmarkus
Tags:           CLI SYSTEM
Comments:       Binaries only
                ----
                Compiled for piCore 8.x
                ----
                Run ntpd as root to start daemon.
                Add /usr/local/bin/ntpd to /opt/bootlocal.sh
                to autostart.
                Default configuration file must work
                in most cases, no customization needed.
                Add /var/lib/ntp to backup to keep drift
                value over reboots.
Change-log:     ----
Current:        2016/05/29 First version, 4.2.8p7

Code: [Select]
tc@box:~$ ldd /usr/local/bin/ntpdate
        linux-vdso.so.1 (0x7ee38000)
        libcap.so.2 => /usr/local/lib/libcap.so.2 (0x76f4d000)
        libm.so.6 => /lib/libm.so.6 (0x76ee0000)
        libssl.so.1.0.0 => not found
        libcrypto.so.1.0.0 => not found
        libpthread.so.0 => /lib/libpthread.so.0 (0x76eb6000)
        libc.so.6 => /lib/libc.so.6 (0x76d74000)
        /lib/ld-linux-armhf.so.3 (0x76f62000)

It seems it still depends on 1.0

I've add in bootlocal.sh

Code: [Select]
ln -sf /tmp/tcloop/openssl/usr/local/lib/libssl.so /usr/lib/libssl.so.1.0.0
ln -sf /tmp/tcloop/openssl/usr/local/lib/libcrypto.so /usr/lib/libcrypto.so.1.0.0
ldconfig -v

than it works properly

    [EDIT]: Added code tags.  Rich
« Last Edit: June 20, 2020, 05:37:30 AM by Rich »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12385
Re: ntpdate refers to wrong library name
« Reply #3 on: June 20, 2020, 01:07:26 AM »
The dependency on openssl is recursive, which is probably why it slipped through the net - ntp will need to be recompiled.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8104
Re: ntpdate refers to wrong library name
« Reply #4 on: June 20, 2020, 05:38:22 AM »
Hi iwkse
Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

Quote
[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:
Code: [Select]
[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.
« Last Edit: August 01, 2020, 10:24:42 AM by Rich »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12385
Re: ntpdate refers to wrong library name
« Reply #5 on: June 21, 2020, 03:03:27 AM »
ntp updated

Offline iwkse

  • Newbie
  • *
  • Posts: 8
Re: ntpdate refers to wrong library name
« Reply #6 on: June 22, 2020, 02:34:15 AM »
Thanks for the info Rich, I will do. Thanks Juanito for the update!