It is recommended to build X either with USE=dlloader or USE=static when using hardened gcc. However, the xorg ebuild does not check that either of these flags is set, and happily produces garbled binaries. Using dlloader solved the issue for me on ppc and x86 Reproducible: Always Steps to Reproduce: 1. put hardened into USE flags 2. emerge gcc 3. emerge xorg-x11 Actual Results: X does not start Expected Results: ebuilds either refuses to build due to invalid USE combo or automatically adds dlloader for hardened gcc
hardened profile sets USE=dlloader flag automatically... Set correct profile when using hardened toolchain.