Please check whether the use of 'einstall' in this ebuild is actually needed. From a quick glance at the Makefile, it seems to have proper support for DESTDIR. Therefore, if possible please replace the call to 'einstall' with proper 'default' or 'emake DESTDIR="${D}" install'. Thanks.
This ebuild needs from scratch rewriting and should rely on Ant instead of the traditional autoconf tools. Why? because gnu-crypto is shipped with one and it flawlessly works out of the box. See: epsilon gnu-crypto-2.0.1 # pwd /var/tmp/portage/dev-java/gnu-crypto-2.0.1-r2/work/gnu-crypto-2.0.1 epsilon gnu-crypto-2.0.1 # ls | grep build build.xml epsilon gnu-crypto-2.0.1 # ant -f build.xml jar Buildfile: /var/tmp/portage/dev-java/gnu-crypto-2.0.1-r2/work/gnu-crypto-2.0.1/build.xml -init: [...] compile: jar: [jar] Building jar: /var/tmp/portage/dev-java/gnu-crypto-2.0.1-r2/work/gnu-crypto-2.0.1/lib/gnu-crypto.jar BUILD SUCCESSFUL Total time: 8 seconds
+*gnu-crypto-2.0.1-r3 (06 Jul 2015) + + 06 Jul 2015; Patrice Clement <monsieurp@gentoo.org> + +gnu-crypto-2.0.1-r3.ebuild: + EAPI 5 bump. Rewrite ebuild from scratch and use Ant instead of autools. Fix + bug 521430. Arch teams, Please stabilise: =dev-java/gnu-crypto-2.0.1-r3 Target arches: amd64 ppc ppc64 x86
amd64 stable
x86 stable
ppc stable
commit 7ab0a92 (HEAD, master) Author: Patrice Clement <monsieurp@gentoo.org> Date: Tue Aug 25 21:54:09 2015 +0000 dev-java/gnu-crypto: Stable for ppc64 using the ALLARCHES policy. Fixes bug 521430. Package-Manager: portage-2.2.18 Signed-off-by: Patrice Clement <monsieurp@gentoo.org
