Date: Sun, 12 May 2019 10:58:19 +0400 From: Gleb Popov <arrowd@freebsd.org> To: Rainer Hurling <rhurlin@gwdg.de> Cc: "haskell@freebsd.org" <haskell@freebsd.org> Subject: Re: textproc/hs-pandoc: Can't build because of broken JuicyPixels Message-ID: <CALH631msJGVDhGKWyxCam7jDcOiXZ_WmttWkR6NgqAZi5z4Hyw@mail.gmail.com> In-Reply-To: <afcd5223-0b25-35b3-f413-5feb0e293085@gwdg.de> References: <452774a7-ec31-2dd0-3ef9-1ce9e11bdd53@gwdg.de> <CALH631m8Q2P5Xbv=ZiQKTkV9uHbm%2BQxk_sifJ6hn8yLikPdoBA@mail.gmail.com> <afcd5223-0b25-35b3-f413-5feb0e293085@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 12, 2019 at 1:08 AM Rainer Hurling <rhurlin@gwdg.de> wrote: > Am 10.05.19 um 14:54 schrieb Gleb Popov: > > > > On Fri, May 10, 2019 at 3:00 PM Rainer Hurling <rhurlin@gwdg.de <mailto: > rhurlin@gwdg.de>> wrote: > > > > Dear list, > > > > After the updates of ghc and hs-ports hit the tree, I try to update > > textproc/hs-pandoc. Unfortunately, cabal can not built JuicyPixels: > > > > > > [..snip..] > > Configuring library for JuicyPixels-3.3.3.. > > Preprocessing library for JuicyPixels-3.3.3.. > > Building library for JuicyPixels-3.3.3.. > > [ 1 of 30] Compiling Codec.Picture.InternalHelper ( > > src/Codec/Picture/InternalHelper.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/InternalHelper.o > > ) > > [ 2 of 30] Compiling Codec.Picture.Metadata.Exif ( > > src/Codec/Picture/Metadata/Exif.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/Metadata/Exif.o > > ) > > [ 3 of 30] Compiling Codec.Picture.Metadata ( > > src/Codec/Picture/Metadata.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/Metadata.o > > ) > > [ 4 of 30] Compiling Codec.Picture.Tiff.Internal.Types ( > > src/Codec/Picture/Tiff/Internal/Types.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/Tiff/Internal/Types.o > > ) > > [ 5 of 30] Compiling Codec.Picture.Tiff.Internal.Metadata ( > > src/Codec/Picture/Tiff/Internal/Metadata.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/Tiff/Internal/Metadata.o > > ) > > [ 6 of 30] Compiling Codec.Picture.Types ( > src/Codec/Picture/Types.hs, > > > /usr/ports/textproc/hs-pandoc/work/pandoc-2.7.1/dist-newstyle/build/x86_64-freebsd/ghc-8.6.3/JuicyPixels-3.3.3/build/Codec/Picture/Types.o > > ) > > ghc: internal error: m32_allocator_init: Failed to map > > (GHC version 8.6.3 for x86_64_portbld_freebsd) > > Please report this as a GHC bug: > http://www.haskell.org/ghc/reportabug > > cabal: Failed to build JuicyPixels-3.3.3 (which is required by > > exe:pandoc from > > pandoc-2.7.1). The build process terminated with exit code -6 > > *** Error code 1 > > Stop. > > make[1]: stopped in /usr/ports/textproc/hs-pandoc > > *** Error code 1 > > > > > > This is on 13-0 CURRENT amd64 r347130. I need Pandoc for my daily > work > > with math/R. > > > > Any help is really appreciated. Thanks in advance. > > > > > > I wasn't able to reproduce this locally, although I have a bit earlier > world revision. But the error message resembles an out of memory one. Have > you tried building pandoc again? > > Thanks for the response and sorry for the late answer. > > Unfortunately, the error also occurs on Poudriere, on two boxes with older > hardware (AMD Phenom II X6 1090T and Intel Core i7-2760QM). Building pandoc > again, even with -DMAKE_JOBS_DISABLE=yes does not help. > Does the error occurs in the same place? That is, when compiling [ 6 of 30] Compiling Codec.Picture.Types module? Do you have any additional knobs set in make.conf? Another thing to try is to rebuild lang/ghc port or send me your ghc executable. > This is with 16 GB RAM and 32 GB swap, SSD has 25 GB of free mem. So I > would expect, that this is not an 'out of memory' problem. > > > > > Regards, > > Rainer Hurling > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631msJGVDhGKWyxCam7jDcOiXZ_WmttWkR6NgqAZi5z4Hyw>