* QA Notice: Files built without respecting CFLAGS have been detected
* Please include the following list of files in your report:
Created attachment 390442 [details]
lto1: out of memory allocating 16711417868 bytes after a total of 274432 bytes
lto-wrapper: /usr/powerpc64-unknown-linux-gnu/gcc-bin/4.8.4/powerpc64-unknown-linux-gnu-gcc returned 1 exit status
/usr/lib/gcc/powerpc64-unknown-linux-gnu/4.8.4/../../../../powerpc64-unknown-linux-gnu/bin/ld: lto-wrapper failed
collect2: error: ld returned 1 exit status
That's a lot of bytes.
The problem persists in 1.5.2.
(In reply to Jeroen Roovers from comment #2)
Thanks for the hint on -flto. Disabling that resolves the CFLAGS issue; I believe LTO strips the flags information from the final objects.
+ 05 May 2015; Mike Gilbert <firstname.lastname@example.org> unbound-1.5.1-r2.ebuild,
+ unbound-1.5.2.ebuild, unbound-1.5.3.ebuild:
+ Disable -flto via configure, bug 530928.