./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/clamav-0.103.0-r1 --htmldir=/usr/share/doc/clamav-0.103.0-r1/html --with-sysroot=/ --libdir=/usr/lib64 --enable-bzip2 --disable-clamonacc --disable-clamdtop --enable-ipv6 --disable-milter --disable-check --without-xml --with-iconv --without-libjson --disable-libclamav-only --with-libcurl --with-system-libmspack --cache-file=/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0/config.cache --disable-experimental --disable-static --disable-zlib-vcheck --enable-id-check --with-dbdir=/var/lib/clamav --with-zlib --disable-llvm --enable-openrc --runstatedir=/run configure: error: unrecognized option: `--runstatedir=/run' Try `./configure --help' for more information * ERROR: app-antivirus/clamav-0.103.0-r1::gentoo failed (configure phase): * econf failed * Reproducible: Always
This would happen if you have =sys-devel/autoconf-2.69-r4 installed instead of current =sys-devel/autoconf-2.69-r5 (which was stabilized for amd64 25 days ago).
Thanks for the hint Ionen.
I can confirm. Update from -r4 to -r5 and all went much further along. Still getting libtool warnings of the form: /bin/mkdir -p '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/image/usr/bin' /bin/sh ../libtool --mode=install /usr/lib/portage/python3.7/ebuild-helpers/xattr/install -c clambc '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/image/usr/bin' libtool: warning: '../libclamav/libclamav.la' has not been installed in '/usr/lib64' libtool: install: /usr/lib/portage/python3.7/ebuild-helpers/xattr/install -c .libs/clambc /var/tmp/portage/app-antivirus/clamav-0.103.0-r1/image/usr/bin/clambc But the real kicker ends up being keepdir; /usr/bin/install: invalid group ‘clamav’ * ERROR: app-antivirus/clamav-0.103.0-r1::gentoo failed (install phase): * dodir failed * * If you need support, post the output of `emerge --info '=app-antivirus/clamav-0.103.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-antivirus/clamav-0.103.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * S: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' /usr/lib/portage/python3.7/ebuild-helpers/keepdir: line 15: /var/tmp/portage/app-antivirus/clamav-0.103.0-r1/image/var/lib/clamav/.keep_app-antivirus_clamav-0: No such file or directory !!! keepdir: cannot write .keep in /var/tmp/portage/app-antivirus/clamav-0.103.0-r1/image/var/lib/clamav * ERROR: app-antivirus/clamav-0.103.0-r1::gentoo failed (install phase): * keepdir failed * * If you need support, post the output of `emerge --info '=app-antivirus/clamav-0.103.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-antivirus/clamav-0.103.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * S: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * Messages for package app-antivirus/clamav-0.103.0-r1: * ERROR: app-antivirus/clamav-0.103.0-r1::gentoo failed (install phase): * dodir failed * * If you need support, post the output of `emerge --info '=app-antivirus/clamav-0.103.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-antivirus/clamav-0.103.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * S: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * ERROR: app-antivirus/clamav-0.103.0-r1::gentoo failed (install phase): * keepdir failed * * If you need support, post the output of `emerge --info '=app-antivirus/clamav-0.103.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-antivirus/clamav-0.103.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' * S: '/var/tmp/portage/app-antivirus/clamav-0.103.0-r1/work/clamav-0.103.0' The clamav group makes no sense: tauri ~ # getent group clamav clamav:x:1012: ... not out of disk space ... and that's all I have time for right now.
I should have >= autoconf-2.69-r5 in BDEPEND, since we do need that latest stable version. The runstatedir patch will be part of the upstream release 2.70 in the next month or so. The clamav group issue is more confusing. Is this a cross-compile? We have acct-group/clamav in DEPEND, which the PMS says is guaranteed to be available during src_install(), but... I don't know.
(In reply to Michael Orlitzky from comment #4) > The clamav group issue is more confusing. Is this a cross-compile? We have > acct-group/clamav in DEPEND, which the PMS says is guaranteed to be > available during src_install(), but... I don't know. I agree. It is confusing as there is nothing unusual about this installation. No, it's not a cross compile. I have seen some strange things with (I suspect) sandbox recently though (can't even get hold of hostname for example, which I need for other internal packages). To make it more confusing ... it worked this time around. So my suggestion is deal with the autoconf issue and ignore the group issue for now (and close this bug). Can't reproduce, so no way to help you get at a resolution for that.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=854fe23b4b7a94a5f65377f486d9cdf314145177 commit 854fe23b4b7a94a5f65377f486d9cdf314145177 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2020-09-30 11:24:24 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2020-09-30 11:33:39 +0000 app-antivirus/clamav: add lower bound on sys-devel/autoconf. We need the runstatedir patch that was added in autoconf-2.69-r5, so this commit adds the lower bound in BDEPEND. This should ensure that anyone upgrading after a few months pulls in the new autoconf before the new clamav. Closes: https://bugs.gentoo.org/744640 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> app-antivirus/clamav/clamav-0.103.0-r1.ebuild | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
