https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-db/gqlplus-1.16 fails to compile (Failed Running automake !). Discovered on: amd64 (internal ref: tinderbox)
Created attachment 692709 [details] build.log build log and emerge --info
Created attachment 692712 [details] 1-automake.out 1-automake.out
Possible context of error(s): * Failed Running automake ! * Failed Running automake !
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cea282fd370362d635943b7bb1ea404bc78db8d2 commit cea282fd370362d635943b7bb1ea404bc78db8d2 Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2021-03-21 12:42:12 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2021-03-21 12:43:15 +0000 dev-db/gqlplus-1.16-r1: revbump to pull in some fixes Bug: https://bugs.gentoo.org/777504 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Fabian Groffen <grobian@gentoo.org> dev-db/gqlplus/Manifest | 1 + .../{gqlplus-1.16.ebuild => gqlplus-1.16-r1.ebuild} | 15 +++++++++++---- 2 files changed, 12 insertions(+), 4 deletions(-)
I don't quite get the automake version mismatch (apparently the (only?) error here), I have 1.16 too, but I tried to address the warnings, for as much relevant in 1.16-r1. (e.g. MKDIR_P isn't used at all?) Not closing, I don't think this is fixed yet, and I can't reproduce.
(In reply to Fabian Groffen from comment #5) > Not closing, I don't think this is fixed yet, and I can't reproduce. There's not much point in those bugs anymore, the cause is known (and widespread). This either need to be fixed in autotools.eclass (there's a workaround), or upstream autoconf:2.71 To reproduce, keep retrying "clean prepare" until it fails, it's kind of random and hard to reproduce (ever) depending on hardware (the faster the cpu is, the easier it seems to be reproduce).
(In reply to Ionen Wolkens from comment #6) > the cause is known Well, loosely known, it still need more digging for a non-portage reproducer.
