svn commit: r486562 - head/security/clamav
Yasuhiro KIMURA
yasu at utahime.org
Sun Dec 9 09:40:11 UTC 2018
From: Yasuhiro KIMURA <yasu at utahime.org>
Subject: Re: svn commit: r486562 - head/security/clamav
Date: Sun, 09 Dec 2018 08:27:17 +0900 (JST)
> Thank you. I'll investigate them.
According to error log, direct problem is that
${PREFIX}/include/clamav.h includes 'cltypes.h' but no such file is installed.
But there is another problem that ${PREFIX}/include/clamav-config.h
includes 'platform.h' which doesn't exist. So I created following
patch.
Index: Makefile
===================================================================
--- Makefile (revision 486932)
+++ Makefile (working copy)
@@ -2,7 +2,7 @@
PORTNAME= clamav
PORTVERSION= 0.101.0
-PORTREVISION= 1
+PORTREVISION= 2
CATEGORIES= security
MASTER_SITES= http://www.clamav.net/downloads/production/
@@ -174,7 +174,8 @@
fi
post-install:
- ${INSTALL_DATA} ${WRKSRC}/clamav-config.h ${STAGEDIR}${PREFIX}/include
+ ${INSTALL_DATA} ${WRKSRC}/clamav-config.h ${WRKSRC}/libclamav/cltypes.h ${WRKSRC}/platform.h \
+ ${STAGEDIR}${PREFIX}/include/
@${MKDIR} ${STAGEDIR}${DOCSDIR}/html \
${STAGEDIR}${DBDIR} \
${STAGEDIR}${LOGDIR} \
Index: pkg-plist
===================================================================
--- pkg-plist (revision 486932)
+++ pkg-plist (working copy)
@@ -58,6 +58,8 @@
bin/sigtool
include/clamav-config.h
include/clamav.h
+include/cltypes.h
+include/platform.h
lib/libclamav.so
lib/libclamav.so.9
lib/libclamav.so.9.0.0
By applying it build of mail/qsheff is fixed. But builds of other
ports are still broken.
https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/112amd64-local/2018-12-09_15h32m01s/logs/errors/clamcour-0.3.8_9.log
https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/112amd64-local/2018-12-09_16h01m47s/logs/errors/havp-0.91_6.log
https://www.utahime.org/FreeBSD/poudriere/data/logs/bulk/112amd64-local/2018-12-09_16h06m11s/logs/errors/p5-Mail-ClamAV-0.29_4.log
According to these logs, it seems API change of libclamav in 0.101.0
is root cause of breakage and cannot be fixed unless upstream of these
ports support new API. So I would like to close this problem by
marking threse ports BROKEN.
---
Yasuhiro KIMURA
More information about the svn-ports-all
mailing list