Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#70987 - [nemiver] FTBFS
Attached to Project:
Community Packages
Opened by loqs (loqs) - Saturday, 22 May 2021, 10:16 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 24 May 2021, 20:47 GMT
Opened by loqs (loqs) - Saturday, 22 May 2021, 10:16 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 24 May 2021, 20:47 GMT
|
DetailsDescription:
nemiver fails to generate its configure script [1]. I failed to find the cause of the failure so as a workaround I switched to building from a tarball already containing configure [2]. Additional info: * nemiver 0.9.6-8 [1] nemiver-0.9.6-8-x86_64-prepare.log [2] PKGBUILD.diff Steps to reproduce: Build package in a clean chroot. |
nemiver-0.9.6-8-x86_64-prepar...
This task depends upon
/usr/share/aclocal/pkg.m4 contains PKG_CHECK_EXISTS but aclocal/autoconf can't see it, for some reason.
I also tried copying in /usr/share/aclocal/* to the m4/ directory, and setting ACLOCAL_PATH, ACLOCAL_AMFLAGS and AL_PATH, but it made no difference.
My next plan is to place the contents of pkg.m4 directly into the autconf file that comes with nemiver and see if that helps. I have my doubts, though.
Knowing autoconf, it's probably a missing ], variable or executable test somewhere that makes the rest of the file act weird.