I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :( The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB). For the moment I've given up on building Ghc especially for use in [haskell]. In order to move on I'll instead make use of Ghc out of [extra]. If anyone has any objections to that, then please speak up. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
My work machine has 8 GB free, if you need any memory-intensive stuff
compiled.
-Leif
On Fri, Jun 15, 2012 at 12:54 PM, Magnus Therning
I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :(
The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB).
For the moment I've given up on building Ghc especially for use in [haskell]. In order to move on I'll instead make use of Ghc out of [extra]. If anyone has any objections to that, then please speak up.
/M
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
I'll be compiling it myself anyway but with this patch added: http://hackage.haskell.org/trac/ghc/ticket/3858 ... if there is an interest having the patch there. I'm typically adding two more patches (but I can skip these for you if you do not like it): * add "breakTick" id to break point list and the information about ignored breakpoint; this is interesting when you want to find out which breakpoint was ignored; it is very dirty workaround for http://hackage.haskell.org/trac/ghc/ticket/2950 I did not have time to do a proper patch. * I'm adding 0.1s delay when printing ghci prompt. Another dirty way to get proper interleaving of stderr/stdout when stderr is coloured using something like http://www.hck.sk/users/peter/pub/colorize.c I use it to get all stderr in red (stdout is default black), and still achieve proper interleaving of stderr text with stdout text. It is quite possible this patch is not needed any more but it was needed when haskeline was introduced the first time. I do not know why, ghci was the only thing which showed any issues. I have 16GiB, so if the only problem is the memory, then I'll be quick. Otherwise, I do not mind if you use ghc from [extra]. There is no special reason not to use [extra] version except extra maintainers can break our dependencies if they do unexpected recompile probably with some significant patches. Although every recompile can break dependencies, mostly it does not happen. You can just place copy of the [extra] version in [haskell] and there should not be any problem at all since you would be in charge of any ghc update. We would mirror only the ghc package in [haskell]. Peter. On 06/15/2012 09:54 PM, Magnus Therning wrote:
I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :(
The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB).
For the moment I've given up on building Ghc especially for use in [haskell]. In order to move on I'll instead make use of Ghc out of [extra]. If anyone has any objections to that, then please speak up.
/M
_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
On 06/15/2012 09:54 PM, Magnus Therning wrote:
I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :(
The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB).
No it's not a memory problem. I found the same problem with building the docs on 8 GB of tmpfs, and others have found the same problem in other distros, e.g. Debian. Here's what I have in my notes: # Edited build.mk to disable PS and PDF docs, which fail to build (maybe fixed by # using different dblatex version but apparently the doc build is fragile)
My build.mk then has for the perf build: ifeq "$(BuildFlavour)" "perf" # perf matches the default settings, repeated here for comparison: SRC_HC_OPTS = -O -H64m GhcStage1HcOpts = -O -fasm GhcStage2HcOpts = -O2 -fasm GhcHcOpts = -Rghc-timing GhcLibHcOpts = -O2 GhcLibWays += p BUILD_DOCBOOK_PS = NO BUILD_DOCBOOK_PDF = NO I think that those last two assigns will fix the problem at the expense of building only html docs.
Magnus Therning
I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :(
The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB).
Hi Magnus, On Gentoo we build haddock with: runghc Setup.hs configure --ghc-options=-rtsopts https://github.com/gentoo-haskell/gentoo-haskell/blob/master/dev-haskell/had... and then add these options when running haddock: +RTS -K16M -RTS Also this upstream patch is useful to avoid haddock failing on unicode chars: https://github.com/gentoo-haskell/gentoo-haskell/blob/master/dev-haskell/had... Please feel free to use any patches in the Gentoo Haskell overlay: https://github.com/gentoo-haskell/gentoo-haskell Regards, Mark
Please read the info contained in bug 79 before doing the upgrade. https://github.com/archhaskell/habs/issues/79 /M On Fri, Jun 15, 2012 at 09:54:31PM +0200, Magnus Therning wrote:
I've been working on upgrading [haskell] to Ghc 7.4.2 for a few days now. So far no luck :(
The build always fails on creating documentation. Yesterday I resorted to taking the source package from [extra], which is known to build fine... but still it failed on generating the docs. I now suspect this is due to the limited memory available on the machine I use to build (1.5GB).
For the moment I've given up on building Ghc especially for use in [haskell]. In order to move on I'll instead make use of Ghc out of [extra]. If anyone has any objections to that, then please speak up.
/M
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
participants (5)
-
Garry Roseman -
Leif Warner -
Magnus Therning -
Mark Wright -
Peter Hercek