FreeBSD Port: clamav-0.88
bsam at ipt.ru
Fri Feb 17 12:29:01 PST 2006
On Sat, 18 Feb 2006 01:11:28 +1100 Sam Lawrance wrote:
> On 18/02/2006, at 12:38 AM, Chuck Rock wrote:
> > I have a FreeBSD 5.2.1 system that this port is having a problem
> > installing on.
> > I have not had any dificulties with the previous releases on this
> > machine.
> > I tried downloading the port, running make. I got the following.
> > ===> Vulnerability check disabled
> > ===> Found saved configuration for clamav-0.80
> > ===> Extracting for clamav-0.88
> > => Checksum OK for clamav-0.88.tar.gz.
> > ===> Patching for clamav-0.88
> > ===> Applying extra patch
> > /root/modules/clamav/files/extra-patch-libclamav__unrarlib.h
Isn't it a bit strange path?
> > ===> Applying FreeBSD patches for clamav-0.88
> > ===> clamav-0.88 depends on shared library: gmp.6 - found
Hm, it's the same error (see my answer at the "Re: Clamav 0.88 make
problem" thread). Weird, it is also 5.x.
> > ===> Configuring for clamav-0.88
> > ===> Building for clamav-0.88
> > make: cannot open Makefile.
> > *** Error code 2
> > I found this error similar on an online forum, they didn't have any
> > resolution.
> > I checked ownership and directory space, no problems.
> > So I decided to install the package instead.
> > That installed without errors, but when I tried to run freshclam to
> > update
> > the virus database, I received this error.
> > /libexec/ld-elf.so.1: Shared object "libz.so.3" not found
> > I did a locate, and I only have this.
> > /libexec/ld-elf.so.1
> > /usr/libexec/ld-elf.so.1
> > /usr/share/man/man1/ld-elf.so.1.1.gz
> > /var/run/ld-elf.so.hints
> > I have not had any problems before, so I don't know where to turn.
> > I was
> > unable to find any help searching online for these issues. I have
> > about 6
> > FreeBSD servers to update with varying FreeBSD versions from 4.9 to
> > 5.4. I
> > have had no problems like this in the past several ClamAV upgrades.
> You have installed packages built for a newer version of FreeBSD.
> They won't work. Roll back the changes and try to investigate the
> problem with the port. Ideally you should upgrade that machine -
> it's out of support and coming up on two years old.
Boris B. Samorodov, Research Engineer
InPharmTech Co, http://www.ipt.ru
Telephone & Internet Service Provider
More information about the freebsd-ports