"Gary R. Schmidt" <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.

It contains both paths.

> > ldconfig creates  the  necessary  links  and  cache  to  the  most
> > recent  shared  libraries  found  in  the  directories specified on the
> > command line, in the file /etc/ld.so.conf, and in the trusted
> > directories, /lib and /usr/lib (on some 64-bit architectures such as
> > x86-64, lib and /usr/lib  are  the  trusted  directories  for 32-bit
> > libraries, while /lib64 and /usr/lib64 are used for 64-bit libraries).
> >  
> Does this mean that it is no longer possible to produce and install 
> binaries on Linux systems with having to create spec files and generate 
> installation packages for them?

Any chance to get the thing working again? I fear going back to 0.94
is not the best idea.

Kind regards

PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

Attachment: pgpL1UpJKzsZK.pgp
Description: Digitale Signatur von OpenPGP

clamav-users mailing list

Help us build a comprehensive ClamAV guide:


Reply via email to