Created attachment 510348 [details] emerge --info ar rcs libargon2.a src/argon2.o src/core.o src/blake2/blake2b.o src/thread.o src/encoding.o src/opt.o ar: src/argon2.o: No such file or directory
Created attachment 510350 [details] build.log
[ebuild R ] app-crypt/argon2-20161029-r1 USE="static-libs*" It happens during Gentoo installation, when I was emerge cryptsetup (static) for my custom initramfs.
https://github.com/P-H-C/phc-winner-argon2/issues/210 Workaround: MAKEOPTS="-j1" emerge -1 argon2
does this apply only to specific gcc versions?
Tested locally with -j12, it only seems to happen with USE=+static-libs. Should I patch the ebuild to force MAKEOPTS=-j1 in only the +static-libs case, or for safety (maybe it's non-deterministic?), also in the -static-libs case?
I opened a bug upstream and asked them to provide a new release. It's fixed in upstream master, so them tagging a new release would be enough to fix this.
I opened a bug upstream (https://github.com/P-H-C/phc-winner-argon2/issues/237) and asked them to provide a new release. It's fixed in upstream master, so them tagging a new release would be enough to fix this.
I just stumbled upon this bug, too. Apparently upstream has tagged a new release just a few hours ago. https://github.com/P-H-C/phc-winner-argon2/releases/tag/20171227
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ade9cbd223a4d7f6237e5fe3d22c37a08edbab3 commit 1ade9cbd223a4d7f6237e5fe3d22c37a08edbab3 Author: Simon Levermann <simon@slevermann.de> AuthorDate: 2018-01-02 14:20:02 +0000 Commit: Craig Andrews <candrews@gentoo.org> CommitDate: 2018-01-02 15:50:39 +0000 app-crypt/argon2: Version bump to 20171227 Package-Manager: Portage-2.3.19, Repoman-2.3.6 Closes: https://bugs.gentoo.org/641390 app-crypt/argon2/Manifest | 1 + app-crypt/argon2/argon2-20171227.ebuild | 27 +++++++++++++++++++++++++++ 2 files changed, 28 insertions(+)
