Mark wrote:
Now, this is a first. I've always been able to compile clamav
without trouble, until today. FreeBSD 4.11.
asarian-host: {root} % make
===> Found saved configuration for clamav-0.88.1
===> Extracting for clamav-0.88.1
=> Checksum OK for clamav-0.88.1.tar.gz.
===> Patching for clamav-0.88.1
===> Applying extra patch
/temp/clamav/files/extra-patch-libclamav__unrarlib.h
===> Applying FreeBSD patches for clamav-0.88.1
-e: not found
*** Error code 127
Stop in /temp/clamav.
Now, what is going on? The extra-patch-libclamav__unrarlib.h
certainly exists.
clamav-0.88.1 builds fine under FreeBSD 4.11 here. I'd assume from the
"/temp/clamav" path above that you're not building from a complete
/usr/ports distribution; perhaps you're missing some Makefile glue from
/usr/ports/Mk, as the clamav port Makefile uses "sed -e":
SUB_FILES= pkg-install pkg-deinstall
SUB_LIST= DBDIR=${DBDIR} \
LOGDIR=${LOGDIR} \
RUNDIR=${RUNDIR} \
CLAMAVUSER=${CLAMAVUSER} \
CLAMAVGROUP=${CLAMAVGROUP} \
CLAMAV_CLAMD_SOCKET=${CLAMAV_CLAMD_SOCKET} \
CLAMAV_MILTER_SOCKET=${CLAMAV_MILTER_SOCKET}
SED_CONF= -E -e 's|^\#?(Example)$$|\#\1|' \
-e 's|^\#?((Update)?LogFile) .*/([a-z]+\.log)$$|\1
${LOGDIR}/\3|' \
-e 's|^\#?(PidFile) .*/([a-z]+\.pid)$$|\1 ${RUNDIR}/\2|' \
-e 's|^\#?(LocalSocket) .*$$|\1 ${CLAMAV_CLAMD_SOCKET}|' \
-e 's|^\#?(User) .*$$|\1 ${CLAMAVUSER}|' \
-e 's|^\#?(AllowSupplementaryGroups)$$|\1|' \
-e 's|^\#?(ScanMail)$$|\1|' \
-e 's|^\#?(NotifyClamd)$$|\1|' \
-e 's|^\#?(DatabaseDirectory) .*$$|\1 ${DBDIR}|' \
-e 's|^\#?(DatabaseOwner) .*$$|\1 ${CLAMAVUSER}|' \
-e 's|^\#?(FixStaleSocket)$$|\1|'
PLIST_SUB+= CLAMAVUSER=${CLAMAVUSER} \
CLAMAVGROUP=${CLAMAVGROUP}
-----
You're likely to get better support about FreeBSD ports-related problems on
the <[EMAIL PROTECTED]> mailing list than here, but if the locals
are curious about the patch mentioned above:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/security/clamav/files/
--
-Chuck
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
