I hit bug #601990 and found a way to make it work, but I believe that the proper fix is to update this package to use the latest I2P software 0.9.33 which does not exhibit the same failure. Starting from the existing ebuild (nativebiginteger-0.8.7.ebuild): * I updated two patches that did not apply anymore. * The lib libjcpuid-x86-linux.so is now produced as libjcpuid-amd64-linux.so so I added a symlink in the ebuild with the old name so that it is still found. * Made it respect CFLAGS for that last lib. Reproducible: Always
Created attachment 524340 [details] New ebuild for i2p 0.9.33.
Created attachment 524342 [details, diff] Re-based build-system patch to respect CFLAGS for building jbigi.
Created attachment 524344 [details, diff] nativebiginteger-0.9.33-jcpuid-build-system.patch Respect CFLAGS and LDFLAGS when building jcpuid.
Created attachment 524346 [details] nativebiginteger-0.9.33.ebuild New ebuild for i2p 0.9.33. (Fixed file name)
Created attachment 524348 [details, diff] nativebiginteger-0.9.33-build-system.patch Re-based build-system patch to respect CFLAGS for building jbigi. (Fixed file name)
The newest in portage is 0.9.48 so I propose closing this as FIXED.