My older slackware install also needed ldconfig run after a from source
install. Without that, I experienced the same errors. I note that ldconfig is
suggested in the source install instructions currently on the web site, but
never had to do it before. Ah, changes :)
> From: Andreas Meyer <a.me...@nimmini.de <mailto:a.me...@nimmini.de>>
> Subject: Re: [clamav-users] error while loading shared libraries
> Date: April 15, 2018 at 10:45:24 AM CDT
> To: email@example.com <mailto:firstname.lastname@example.org>
> "Gary R. Schmidt" <grschm...@acm.org <mailto:grschm...@acm.org>> schrieb am
> 16.04.18 um 00:48:10 Uhr:
>>>> Hmm, I just built it on an OpenSUSE system (I mainly use Solaris), and
>>>> had the same problem. Which is interesting as /etc/ld.so.conf contains
>>>> /usr/local/lib64, so it should find libclammspack.so.0 there.
>>> and youd did call "ldconfig"?
>> No, the OpenSUSE system is basically as it came out of the box, and
>> given that /etc/ld.so.conf contains /usr/local/lib64 by default I am
>> surprised that ldconfig would be needed.
> hmmm, after a ldconfig freshclam and clamd are running again.
> PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1
> clamav-users mailing list
> email@example.com <mailto:firstname.lastname@example.org>
> Help us build a comprehensive ClamAV guide:
clamav-users mailing list
Help us build a comprehensive ClamAV guide: