x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-no-pie' `x86_64-pc-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) configure: error: Building ghc-pwd failed !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-lang/ghc-8.0.2/work/ghc-8.0.2/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_libressl_20180219-235058 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-lang/ghc [nomerge ] dev-lang/ghc-8.0.2 USE="gmp profile -binary -doc -ghcbootstrap -ghcmakebinary" [ebuild N ] app-admin/haskell-updater-1.2.12 [ebuild N ] dev-lang/ghc-8.0.2 USE="gmp profile -binary -doc -ghcbootstrap -ghcmakebinary"
Created attachment 520326 [details] emerge-info.txt
Created attachment 520328 [details] dev-lang:ghc-8.0.2:20180220-181752.log
Created attachment 520330 [details] emerge-history.txt
Created attachment 520332 [details] environment
Created attachment 520334 [details] etc.portage.tbz2
Created attachment 520336 [details] logs.tbz2
Created attachment 520338 [details] temp.tbz2
I think this error is caused by gcc-5.4.0. gcc-6 should be fine. 17.0 profiles do mask <gcc-6. Is use of gcc-5.4.0 intentional?
(In reply to Sergei Trofimovich from comment #8) for 1 image I reactivated it but plan to do it on a small fraction of images (maybe 10% ?)
*** Bug 664492 has been marked as a duplicate of this bug. ***
Closing as obsolete, presuming GCC-6+ is fine.
