dev-libs/libgcrypt still wants automake-1.12 but it builds fine with automake-1.14*.
This issue probably appeared because old versions of libgcrypt requires automake <=1.12
Which version of dev-libs/libgcrypt are you talking about?
I'm talking about dev-libs/libgcrypt-1.6.*.
On my system I have only automake-1.14.1 and it builds fine.
(In reply to wojtek from comment #2)
> I'm talking about dev-libs/libgcrypt-1.6.*.
> On my system I have only automake-1.14.1 and it builds fine.
Note the changelog entry for the version bump, specifically "restrict automake version so tests run properly."
If you supply a patch to fix the issue, I'd be glad to unrestrict it.
Created attachment 368568 [details, diff]
fix test with automake>=1.13
Indeed. Tests fails on my system too with automake>=1.13
changelog from 1.12.5 says:
"Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
option) will become the default one; the older serial testsuite
harness will still be available through the use of the 'serial-tests'
Attached patch fix problems with tests and now everything is OK
====================(In reply to wojtek from comment #4)
> Indeed. Tests fails on my system too with automake>=1.13
Sorry. I tested only with automake-1.14
All 23 tests passed
(1 test was not run)
I suggest to delete 'WANT_AUTOMAKE=1.13' assignment in ebuild. 'WANT_AUTOMAKE=1.13' results in '=sys-devel/automake-1.13*' dependency, not '>=sys-devel/automake-1.13'.
$ portageq metadata / ebuild dev-libs/libgcrypt-1.6.0-r1 DEPEND
>=dev-libs/libgpg-error-1.11 !<sys-devel/gettext-0.18.1.1-r3 =sys-devel/automake-1.13* >=sys-devel/autoconf-2.68 sys-devel/libtool
Fixed in 1.6.1.