Linking rocketwiki-lqfb ... /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: rocketwiki-lqfb.o: relocation R_X86_64_32S against `.text' can not be used when making a PIE object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/parsec-3.1.11/ghc-7.10.3/libHSparsec-3.1.11-FHQ9LP7WTfzFhoLjhQRK7d.a(Prim.o): relocation R_X86_64_32S against `.text' can not be used when making a PIE object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/parsec-3.1.11/ghc-7.10.3/libHSparsec-3.1.11-FHQ9LP7WTfzFhoLjhQRK7d.a(Char.o): relocation R_X86_64_32S against symbol `stg_upd_frame_info' can not be used when making a PIE object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/parsec-3.1.11/ghc-7.10.3/libHSparsec-3.1.11-FHQ9LP7WTfzFhoLjhQRK7d.a(Combinator.o): relocation R_X86_64_32S against symbol `stg_upd_frame_info' can not be used when making a PIE object; recompile with -fPIC ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_20181006-210241 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby25 (with Rubygems) * emerge -qpvO www-apps/rocketwiki-lqfb [ebuild N ] www-apps/rocketwiki-lqfb-0.4
Created attachment 550760 [details] emerge-info.txt
Created attachment 550762 [details] emerge-history.txt
Created attachment 550764 [details] environment
Created attachment 550766 [details] etc.portage.tbz2
Created attachment 550768 [details] temp.tbz2
Created attachment 550770 [details] www-apps:rocketwiki-lqfb-0.4:20181011-180934.log
*** This bug has been marked as a duplicate of bug 622670 ***