Package: src:haskell-http-link-header Version: 1.0.3-3 Tags: patch pending User: [email protected] Usertags: ppc64el
-- Dear maintainer, I see that the package fails to build ppc64el (but also powerpc/ppc64). Running the build several times, I see it can fails differently and especially during the compilation, so not sure about this particular package being the cause. There are some traces in dmesg like : [124845.158532] ghc_worker[37823]: unhandled signal 11 at 38426c883c4c03dc nip 38426c883c4c03dc lr 00003fff713ae134 code 30003 [125617.514575] ghc_worker[42842]: unhandled signal 11 at 0000000000000009 nip 00003fff79f3b7f0 lr 00003fff7211e134 code 30001 [125727.370133] ghc_worker[43624]: unhandled signal 11 at 5100003fffa5c2cc nip 5100003fffa5c2cc lr 00003fff9cdce134 code 30003 [126077.784174] ghc_worker[47413]: unhandled signal 11 at 0000000000000000 nip 00003fffa2fc8034 lr 00003fffa2fce134 code 30001 ... and looking at ghc's upstream, I see this bug opened : https://ghc.haskell.org/trac/ghc/ticket/12537 On my side I can see : $ gdb /usr/lib/ghc/bin/ghc /tmp/core.ghc_worker.52783.forge.1506076822 ... [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/ghc/bin/ghc -B/usr/lib/ghc --make -no-link -fbuilding-cabal-package -O'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x384264ac3c4c02e4 in ?? () [Current thread is 1 (Thread 0x3eff1f7ff1a0 (LWP 52814))] (gdb) bt #0 0x384264ac3c4c02e4 in ?? () #1 0x00003fff79a5e134 in stg_atomicModifyMutVarzh () from /usr/lib/ghc/bin/../rts/libHSrts_thr-ghc8.0.2.so #2 0x00003fff79a2f424 in ?? () from /usr/lib/ghc/bin/../rts/libHSrts_thr-ghc8.0.2.so #3 0x00003fff79a30ea8 in ?? () from /usr/lib/ghc/bin/../rts/libHSrts_thr-ghc8.0.2.so #4 0x00003fff79a3eb64 in ?? () from /usr/lib/ghc/bin/../rts/libHSrts_thr-ghc8.0.2.so #5 0x00003fff798e80dc in start_thread () from /lib/powerpc64le-linux-gnu/libpthread.so.0 #6 0x00003fff79681508 in clone () from /lib/powerpc64le-linux-gnu/libc.so.6 I don't know haskell at all, but as the above ticket mentioned problem due to parallel build and atomic operations on Power, I think we have a similar issue. I tried forcing the build with -j1 which didn't break so far while looping on the build of the package. So here is a patch that can workaround that ghc issue on Power for now. Regards. F.
diff -Nru haskell-http-link-header-1.0.3/debian/changelog haskell-http-link-header-1.0.3/debian/changelog --- haskell-http-link-header-1.0.3/debian/changelog 2017-07-20 22:03:40.000000000 +0200 +++ haskell-http-link-header-1.0.3/debian/changelog 2017-09-22 11:40:05.000000000 +0200 @@ -1,3 +1,11 @@ +haskell-http-link-header (1.0.3-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules : disable parallel build on powerpc/ppc64el/ppc64 while + waiting for fix of https://ghc.haskell.org/trac/ghc/ticket/12537 + + -- Frédéric Bonnard <[email protected]> Fri, 22 Sep 2017 09:40:05 +0000 + haskell-http-link-header (1.0.3-3) unstable; urgency=medium * debian/patches/59c4bf5c8b2cffb7b293bbc034310914a6c3bd20.patch: diff -Nru haskell-http-link-header-1.0.3/debian/rules haskell-http-link-header-1.0.3/debian/rules --- haskell-http-link-header-1.0.3/debian/rules 2017-06-24 05:32:06.000000000 +0200 +++ haskell-http-link-header-1.0.3/debian/rules 2017-09-22 11:40:05.000000000 +0200 @@ -14,4 +14,10 @@ # Dh_Haskell.sh, so just point it to a writable HOME for now. export HOME=$(CURDIR)/debian/cabalconfig +# workaround to prevent some random failures on power while waiting for : +# https://ghc.haskell.org/trac/ghc/ticket/12537 +ifneq (,$(findstring $(DEB_HOST_ARCH), powerpc ppc64 ppc64el)) +DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-j1" +endif + check-ghc-stamp: export LC_ALL := C.UTF-8
pgpF6BiiXlikU.pgp
Description: PGP signature
_______________________________________________ Pkg-haskell-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers
