This package fails to compile on a stable system. Attached relevant logs and emerge --info
Created attachment 691605 [details] emerge_info emerge --info
Created attachment 691608 [details] app-misc:jq-1.7_pre20201109:20210315-152738.log build log
Created attachment 691611 [details] autoconf.out relevant log
I feel this should be patched out (currently doesn't even depend on git): configure.ac: >m4_define([jq_version], > m4_esyscmd_s([(git rev-parse --verify -q jq-1.0 > /dev/null && > (git describe --tags --dirty --match 'jq-*'|sed 's/^jq-//')) || > echo `git rev-parse --abbrev-ref HEAD`-`git describe --always --dirty`])))
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e850fa723a5ed727bc209b633aa6838e162b129 commit 5e850fa723a5ed727bc209b633aa6838e162b129 Author: Patrick McLean <patrick.mclean@sony.com> AuthorDate: 2021-03-25 18:53:14 +0000 Commit: Patrick McLean <chutzpah@gentoo.org> CommitDate: 2021-03-25 18:53:14 +0000 app-misc/jq-1.7_pre20201109: Add patch for git bdep (bug #776385) Closes: https://bugs.gentoo.org/776385 Copyright: Sony Interactive Entertainment Inc. Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Patrick McLean <chutzpah@gentoo.org> app-misc/jq/files/jq-1.7_pre20201109-no-git-bdep.patch | 13 +++++++++++++ app-misc/jq/jq-1.7_pre20201109.ebuild | 2 ++ 2 files changed, 15 insertions(+)
Reopening as the issue is still here. By manually running autoconf --force in the source directory I get: # autoconf --force configure.ac:10: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:11: error: possibly undefined macro: AM_SILENT_RULES configure.ac:12: error: possibly undefined macro: AM_PROG_AR configure.ac:13: error: possibly undefined macro: AM_MAINTAINER_MODE configure.ac:21: error: possibly undefined macro: AM_PROG_CC_C_O configure.ac:52: error: possibly undefined macro: AM_CONDITIONAL configure.ac:128: error: possibly undefined macro: AC_FIND_FUNC configure.ac:149: error: possibly undefined macro: AC_CHECK_MATH_FUNC I have automake-1.16.2-r1
Can you share the latest logs with the git patch?
(In reply to Sam James from comment #7) > Can you share the latest logs with the git patch? Also, try reinstalling autoconf, m4, automake, autoconf-archive (if installed) just in case? (no binpkg)
(In reply to Sam James from comment #8) > (In reply to Sam James from comment #7) > > Can you share the latest logs with the git patch? > > Also, try reinstalling autoconf, m4, automake, autoconf-archive (if > installed) just in case? (no binpkg) # emerge -q1 autoconf m4 automake autoconf-archive jq >>> Verifying ebuild manifests >>> Emerging (1 of 5) sys-devel/autoconf-archive-2019.01.06::gentoo >>> Installing (1 of 5) sys-devel/autoconf-archive-2019.01.06::gentoo >>> Emerging (2 of 5) sys-devel/m4-1.4.18-r2::gentoo >>> Installing (2 of 5) sys-devel/m4-1.4.18-r2::gentoo >>> Emerging (3 of 5) sys-devel/autoconf-2.69-r5::gentoo >>> Installing (3 of 5) sys-devel/autoconf-2.69-r5::gentoo >>> Emerging (4 of 5) sys-devel/automake-1.16.2-r1::gentoo >>> Installing (4 of 5) sys-devel/automake-1.16.2-r1::gentoo >>> Emerging (5 of 5) app-misc/jq-1.7_pre20201109::gentoo >>> Failed to emerge app-misc/jq-1.7_pre20201109, Log file: >>> '/var/log/emerge-log/app-misc:jq-1.7_pre20201109:20210326-205346.log' * * The following package has failed to build, install, or execute postinst: * * (app-misc/jq-1.7_pre20201109:0/0::gentoo, ebuild scheduled for merge), Log file: * '/var/log/emerge-log/app-misc:jq-1.7_pre20201109:20210326-205346.log' *
Created attachment 694587 [details] build.log build log
Created attachment 694590 [details] autoconf.out autoconf.out
Thanks for sharing output, going to think about it. (Re CFLAGS, see https://bugs.gentoo.org/776370#c4.)
This has got to be the same problem as the other bug but I’m baffled at the moment. Is there any chance you could list anything “weird” about the system? Anything different from usual?
Libtool was also broken so I started 'emerge -e world' to see if something will improve. Well it works now, I don't know what exactly was broken but it has not been catched by our tools.
