Bug 583196

Summary:	dev-libs/libgcrypt: Is WANT_AUTOMAKE=1.14 really needed?
Product:	Gentoo Linux	Reporter:	Martin Väth <martin>
Component:	Current packages	Assignee:	Crypto team [DISABLED] <crypto+disabled>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	jstein, k_f
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin Väth 2016-05-16 16:17:19 UTC

Is there a reason why dev-libs/libgcrypt contains WANT_AUTOMAKE=1.14?

I have only automake-1.15-r2 installed, and at least versions 1.6.5 and 1.7.0 compile with it without any problems (on x86 and am64 with gcc-5.3.0) when I remove the WANT_AUTOMAKE line from the ebuild.

Comment 1 Kristian Fiskerstrand (RETIRED) gentoo-dev

2016-05-17 20:36:08 UTC

(In reply to Martin Väth from comment #0)
> Is there a reason why dev-libs/libgcrypt contains WANT_AUTOMAKE=1.14?
> 
> I have only automake-1.15-r2 installed, and at least versions 1.6.5 and
> 1.7.0 compile with it without any problems (on x86 and am64 with gcc-5.3.0)
> when I remove the WANT_AUTOMAKE line from the ebuild.

Changing automake versions is less trivial than one would expect due to incompabilities introduced between versions. For a long time libgcrypt versions needed patches to compile for 1.13 and 1.14, so as such it won't be marked for other (stable) versions without proper testing.