libraries/ghc-prim/cbits/atomic.c: In function ‘hs_atomic_nand8’: libraries/ghc-prim/cbits/atomic.c:127:10: error: note: ‘__sync_fetch_and_nand’ changed semantics in GCC 4.4 return __sync_fetch_and_nand((volatile StgWord8 *) x, (StgWord8) val); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0_libressl_20170826-115304 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * 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.10 [ebuild N ] dev-lang/ghc-8.0.2 USE="gmp profile -binary -doc -ghcbootstrap -ghcmakebinary"
Created attachment 490818 [details] emerge-info.txt
Created attachment 490820 [details] dev-lang:ghc-8.0.2:20170827-031734.log.bz2
Created attachment 490822 [details] emerge-history.txt
Created attachment 490824 [details] environment
Created attachment 490826 [details] etc.portage.tbz2
Created attachment 490828 [details] logs.tbz2
Created attachment 490830 [details] temp.tbz2
> libraries/ghc-prim/cbits/atomic.c:127:10: error: > note: ‘__sync_fetch_and_nand’ changed semantics in GCC 4.4 This is only warning about changes done in gcc-4.4 long ago. The real error is hung (?!) 'as': x86_64-pc-linux-gnu-gcc: internal compiler error: Hangup (program as) Please submit a full bug report, with preprocessed source if appropriate. See <https://bugs.gentoo.org/> for instructions. `x86_64-pc-linux-gnu-gcc' failed in phase `Assembler'. (Exit code: 4) make[1]: *** [libraries/base/ghc.mk:4: libraries/base/dist-install/build/System/IO/Error.p_o] Error 1 Does it reproducibly happens for you?
(In reply to Sergei Trofimovich from comment #8) No, and because that image is somehow wrong (obscure PAM errors) - I'll try to replay that image to see what happened there. So I'll close this bug as a fallout of something other being buggy
(In reply to Toralf Förster from comment #9) FWIW maybe app-shells/push is making trouble ?
(In reply to Toralf Förster from comment #10) > (In reply to Toralf Förster from comment #9) > FWIW maybe app-shells/push is making trouble ? app-shells/push installs a single 'push.sh' script. ghc itself does not use 'push.sh' scripts but maybe something else in the system does and gets into a conflict.
yeah, bug #629030 and bug #629024 indicates that the setup of that images was made wrong. Aaybe a "small, non-intrusive change" (tm) of the tinderbox script from /me is the culprit...
