Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 752975 - dev-libs/libressl-3.2.2: configure.ac:21: error: version mismatch. This is Automake 1.16.1, but the definition used by this AM_INIT_AUTOMAKE comes from Automake 1.16.2.
Summary: dev-libs/libressl-3.2.2: configure.ac:21: error: version mismatch. This is A...
Status: RESOLVED DUPLICATE of bug 752465
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo LibreSSL
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-03 16:33 UTC by Quentin Retornaz
Modified: 2020-11-03 22:35 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,11.77 KB, text/x-log)
2020-11-03 16:34 UTC, Quentin Retornaz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Quentin Retornaz 2020-11-03 16:33:39 UTC
dev-libs/libressl-3.2.2 depends on automake 1.16.2 to build, and then in BDEPEND, the version should be set.
>=sys-devel/automake-1.16.2


Reproducible: Always

Actual Results:  
fails to build saying that automake 1.16.2 should be used

Expected Results:  
should build successfully.
Comment 1 Quentin Retornaz 2020-11-03 16:34:08 UTC
Created attachment 669887 [details]
build.log
Comment 2 Mike Gilbert gentoo-dev 2020-11-03 16:55:09 UTC
The build system should not be calling automake in the first place. There should be no need to depend on a specific version of automake.

The build system is being patched without calling eautoreconf, which causes maintainer mode to call automake automagically.
Comment 3 needle 2020-11-03 17:48:32 UTC
Confirmed. Running into the same bug.
Comment 4 Vincent Grande 2020-11-03 19:43:51 UTC
I’ve been getting this error for about two days as well, I thought it was an issue on my end.

Log:
https://dpaste.com/F5RVBFA8Q
Comment 5 Jory A. Pratt gentoo-dev 2020-11-03 22:35:05 UTC

*** This bug has been marked as a duplicate of bug 752465 ***