From cvs-ghc at haskell.org Fri Jun 1 03:30:01 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Fri Jun 1 03:25:43 2007 Subject: Daily report for head Message-ID: <200706010730.l517U1KG018389@monk.galois.com> Build results: x86-64 Linux head: fail (failed stage1) x86 Windows head: fail (failed stage1) x86 Windows head fast: pass pass pass pass pass pass x86-64 Linux head unreg: fail (failed stage1) Old unexpected test passes: arith008 1 x86 Windows head Old unexpected test failures: GMapAssoc 1 x86 Windows head GMapTop 1 x86 Windows head TH_exn2 1 x86 Windows head fast arith005 1 x86 Windows head arith008 1 x86 Windows head arith011 2 x86 Windows head arith012 1 x86 Windows head barton-mangler-bug 1 x86 Windows head base01 1 x86 Windows head break014 2 x86 Windows head break015 2 x86 Windows head break017 2 x86 Windows head cg002 1 x86 Windows head conc023 1 x86 Windows head conc052 1 x86 Windows head conc057 1 x86 Windows head conc063 1 x86 Windows head drv006 1 x86 Windows head drv008 1 x86 Windows head drv009 1 x86 Windows head drvfail001 2 x86 Windows head drvfail002 2 x86 Windows head drvfail003 2 x86 Windows head drvfail007 2 x86 Windows head dynbrk005 2 x86 Windows head ffi-deriv1 2 x86 Windows head ffi009 1 x86 Windows head gadt23 1 x86 Windows head galois_raytrace 1 x86 Windows head getC 2 x86 Windows head getDirContents001 1 x86 Windows head ghc-e001 2 x86 Windows head ghciprog004 1 x86 Windows head fast haddock.Test 1 x86 Windows head ind2 1 x86 Windows head list001 2 x86 Windows head maessen_hashtab 1 x86 Windows head net001 1 x86 Windows head num012 1 x86 Windows head par001 1 x86 Windows head pkg01 1 x86 Windows head prog003 2 x86 Windows head read008 2 x86 Windows head read016 1 x86 Windows head read025 1 x86 Windows head read040 2 x86 Windows head readwrite002 2 x86 Windows head result001 2 x86 Windows head rn019 1 x86 Windows head rn025 1 x86 Windows head rn026 1 x86 Windows head rn027 1 x86 Windows head rn028 1 x86 Windows head rn029 1 x86 Windows head rn031 1 x86 Windows head rn032 1 x86 Windows head rn033 1 x86 Windows head rn037 1 x86 Windows head rn046 1 x86 Windows head rnfail028 2 x86 Windows head simpl004 1 x86 Windows head simpl007 1 x86 Windows head simplCore.prog002 1 x86 Windows head tc049 2 x86 Windows head tc080 1 x86 Windows head tc127 1 x86 Windows head tcfail046 2 x86 Windows head tcfail072 2 x86 Windows head tcfail105 2 x86 Windows head tcfail118 2 x86 Windows head tcfail140 2 x86 Windows head tcfail145 2 x86 Windows head tcfail169 2 x86 Windows head tcfail177 2 x86 Windows head tcrun022 1 x86 Windows head typecheck.testeq1 1 x86 Windows head -------------- next part -------------- Last 30 lines: use Data.ByteString, Data.ByteString.Char8, or plain String. [2 of 5] Compiling Language.Haskell.TH.PprLib ( Language/Haskell/TH/PprLib.hs, dist/build/Language/Haskell/TH/PprLib.o ) [3 of 5] Compiling Language.Haskell.TH.Ppr ( Language/Haskell/TH/Ppr.hs, dist/build/Language/Haskell/TH/Ppr.o ) [4 of 5] Compiling Language.Haskell.TH.Lib ( Language/Haskell/TH/Lib.hs, dist/build/Language/Haskell/TH/Lib.o ) [5 of 5] Compiling Language.Haskell.TH ( Language/Haskell/TH.hs, dist/build/Language/Haskell/TH.o ) [1 of 5] Compiling Language.Haskell.TH.Syntax ( Language/Haskell/TH/Syntax.hs, dist/build/Language/Haskell/TH/Syntax.p_o ) Language/Haskell/TH/Syntax.hs:48:0: Warning: Module `Data.PackedString' is deprecated: use Data.ByteString, Data.ByteString.Char8, or plain String. Language/Haskell/TH/Syntax.hs:48:0: Warning: Deprecated use of `packString' (imported from Data.PackedString): use Data.ByteString, Data.ByteString.Char8, or plain String. Language/Haskell/TH/Syntax.hs:48:0: Warning: Deprecated use of `unpackPS' (imported from Data.PackedString): use Data.ByteString, Data.ByteString.Char8, or plain String. Language/Haskell/TH/Syntax.hs:48:0: Warning: Deprecated use of type constructor or class `PackedString' (imported from Data.PackedString): use Data.ByteString, Data.ByteString.Char8, or plain String. make[2]: *** [build.library.template-haskell] Error 9 make[2]: Leaving directory `/64playpen/buildbot/x86_64-linux-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/64playpen/buildbot/x86_64-linux-head/build' -------------- next part -------------- Last 30 lines: .\Network\BSD.hsc:136:25: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:171:20: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:196:24: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:329:22: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:330:23: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:372:17: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:528:18: Not in scope: type constructor or class `HostName' <> Reading parameters from c:\builds\slave\x86-win-head\build\libraries\network\network.buildinfo Preprocessing library network-2.0.1... Building network-2.0.1... make[2]: *** [build.library.network] Error 1 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: [134 of 155] Compiling Data.ByteString.Lazy.Char8 ( Data/ByteString/Lazy/Char8.hs, dist/build/Data/ByteString/Lazy/Char8.p_o ) [135 of 155] Compiling GHC.TopHandler ( GHC/TopHandler.lhs, dist/build/GHC/TopHandler.p_o ) [136 of 155] Compiling System.Environment ( System/Environment.hs, dist/build/System/Environment.p_o ) [137 of 155] Compiling Control.Concurrent.MVar ( Control/Concurrent/MVar.hs, dist/build/Control/Concurrent/MVar.p_o ) [138 of 155] Compiling Control.Concurrent.QSem ( Control/Concurrent/QSem.hs, dist/build/Control/Concurrent/QSem.p_o ) [139 of 155] Compiling Control.Concurrent.QSemN ( Control/Concurrent/QSemN.hs, dist/build/Control/Concurrent/QSemN.p_o ) [140 of 155] Compiling Control.Concurrent.SampleVar ( Control/Concurrent/SampleVar.hs, dist/build/Control/Concurrent/SampleVar.p_o ) [141 of 155] Compiling Data.Array.Diff ( Data/Array/Diff.hs, dist/build/Data/Array/Diff.p_o ) [142 of 155] Compiling Data.Unique ( Data/Unique.hs, dist/build/Data/Unique.p_o ) [143 of 155] Compiling Control.Concurrent.Chan ( Control/Concurrent/Chan.hs, dist/build/Control/Concurrent/Chan.p_o ) [144 of 155] Compiling Control.Concurrent ( Control/Concurrent.hs, dist/build/Control/Concurrent.p_o ) [145 of 155] Compiling System.Timeout ( System/Timeout.hs, dist/build/System/Timeout.p_o ) [146 of 155] Compiling Control.Arrow ( Control/Arrow.hs, dist/build/Control/Arrow.p_o ) [147 of 155] Compiling Control.Applicative ( Control/Applicative.hs, dist/build/Control/Applicative.p_o ) [148 of 155] Compiling Data.Foldable ( Data/Foldable.hs, dist/build/Data/Foldable.p_o ) [149 of 155] Compiling Data.IntMap ( Data/IntMap.hs, dist/build/Data/IntMap.p_o ) [150 of 155] Compiling Data.Set ( Data/Set.hs, dist/build/Data/Set.p_o ) [151 of 155] Compiling Data.Traversable ( Data/Traversable.hs, dist/build/Data/Traversable.p_o ) [152 of 155] Compiling Data.Map ( Data/Map.hs, dist/build/Data/Map.p_o ) [153 of 155] Compiling Data.Sequence ( Data/Sequence.hs, dist/build/Data/Sequence.p_o ) [154 of 155] Compiling Data.Tree ( Data/Tree.hs, dist/build/Data/Tree.p_o ) [155 of 155] Compiling Data.Graph ( Data/Graph.hs, dist/build/Data/Graph.p_o ) <> Setup: dist/build/Control/Applicative_split: getDirectoryContents: does not exist (No such file or directory) make[2]: *** [build.library.base] Error 1 make[2]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build' From simonmar at microsoft.com Fri Jun 1 04:27:56 2007 From: simonmar at microsoft.com (Simon Marlow) Date: Fri Jun 1 04:23:37 2007 Subject: patch applied (ghc): remove OpenBSD-specific initAdjustor() code that shouldn't be required now Message-ID: <20070601082756.GA20397@cvs.haskell.org> Fri Jun 1 01:26:48 PDT 2007 Simon Marlow * remove OpenBSD-specific initAdjustor() code that shouldn't be required now Submitted by: Matthias Kilian M ./rts/Adjustor.c -26 M ./rts/RtsStartup.c -3 From simonmar at microsoft.com Fri Jun 1 04:29:24 2007 From: simonmar at microsoft.com (Simon Marlow) Date: Fri Jun 1 04:25:04 2007 Subject: patch applied (ghc): tiny cleanup Message-ID: <20070601082924.GA20474@cvs.haskell.org> Fri May 25 01:22:35 PDT 2007 Simon Marlow * tiny cleanup M ./rts/PrimOps.cmm -2 +2 From simonmar at microsoft.com Fri Jun 1 04:35:14 2007 From: simonmar at microsoft.com (Simon Marlow) Date: Fri Jun 1 04:30:54 2007 Subject: patch applied (ghc): FIX BUILD: GHC doesn't use filepath (yet) Message-ID: <20070601083514.GA20586@cvs.haskell.org> Mon May 21 07:17:45 PDT 2007 Simon Marlow * FIX BUILD: GHC doesn't use filepath (yet) M ./compiler/ghci/InteractiveUI.hs -2 +1 From simonmar at haskell.cs.yale.edu Fri Jun 1 09:31:28 2007 From: simonmar at haskell.cs.yale.edu (Simon Marlow) Date: Fri Jun 1 09:31:30 2007 Subject: patch applied (/haskell/ghc): fix broken links to the building guide Message-ID: <20070601133128.GA20995@haskell.cs.yale.edu> Fri Jun 1 09:35:09 EDT 2007 Simon Marlow * fix broken links to the building guide M ./index.html -2 +2 From cdsmith at twu.net Fri Jun 1 09:47:37 2007 From: cdsmith at twu.net (cdsmith@twu.net) Date: Fri Jun 1 09:43:27 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup Message-ID: Thu May 31 23:36:44 MDT 2007 cdsmith@twu.net * FIX #1378 Add option for a shorter banner on GHCi startup Add -short-ghci-banner and -long-ghci-banner. The default is long, which is the current behavior. The short banner prints a one-line introduction with only the version, web site, and ":? for help" message. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 427664 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/cvs-ghc/attachments/20070601/84478479/attachment-0001.bin From simonmarhaskell at gmail.com Fri Jun 1 09:51:50 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Fri Jun 1 09:47:45 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: References: Message-ID: <46602476.8080303@gmail.com> cdsmith@twu.net wrote: > Thu May 31 23:36:44 MDT 2007 cdsmith@twu.net > * FIX #1378 Add option for a shorter banner on GHCi startup > > Add -short-ghci-banner and -long-ghci-banner. The default is long, which is > the current behavior. The short banner prints a one-line introduction with > only the version, web site, and ":? for help" message. Wow, that patch was nearly 0.5Mb. Can we do something about the patch size? Regarding the patch itself, I'd rather just kill the current banner and replace it with a shorter banner if we're going to do this. What does everyone else think? Cheers, Simon From cdsmith at twu.net Fri Jun 1 09:55:59 2007 From: cdsmith at twu.net (Chris Smith) Date: Fri Jun 1 09:53:37 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup References: <46602476.8080303@gmail.com> Message-ID: <016301c7a454$96175c70$6700a8c0@KYA> Simon Marlow wrote: > Wow, that patch was nearly 0.5Mb. Can we do something about the > patch size? I just did a darcs send. Should I do something different? > Regarding the patch itself, I'd rather just kill the current banner > and replace it with a shorter banner if we're going to do this. What does > everyone else think? Personally, I actually rather like the current banner. I just did this because I'm trying to get familiar with the code, and this was the easiest thing on trac. I'd hate to lose my ASCII art GHCi banner because of it! -- Chris Smith From stefanor at cox.net Fri Jun 1 10:04:35 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Fri Jun 1 10:00:15 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <016301c7a454$96175c70$6700a8c0@KYA> References: <46602476.8080303@gmail.com> <016301c7a454$96175c70$6700a8c0@KYA> Message-ID: <20070601140435.GA3135@localhost.localdomain> On Fri, Jun 01, 2007 at 07:55:59AM -0600, Chris Smith wrote: > Simon Marlow wrote: > >Wow, that patch was nearly 0.5Mb. Can we do something about the > >patch size? > > I just did a darcs send. Should I do something different? > > >Regarding the patch itself, I'd rather just kill the current banner > >and replace it with a shorter banner if we're going to do this. What does > >everyone else think? > > Personally, I actually rather like the current banner. I just did this > because I'm trying to get familiar with the code, and this was the easiest > thing on trac. I'd hate to lose my ASCII art GHCi banner because of it! My 2 cents: I'd like to see the banner removed completely, or at least moved to a higher verbosity level. Users who need help or version are presumably know about --help and --version; they aren't exactly GHC-specific! Stefan From cdsmith at twu.net Fri Jun 1 10:08:16 2007 From: cdsmith at twu.net (Chris Smith) Date: Fri Jun 1 10:05:59 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup References: <46602476.8080303@gmail.com> <016301c7a454$96175c70$6700a8c0@KYA> <20070601140435.GA3135@localhost.localdomain> Message-ID: <018401c7a456$4d597700$6700a8c0@KYA> Stefan O'Rear wrote: > My 2 cents: > > I'd like to see the banner removed completely, or at least moved to a > higher verbosity level. > > Users who need help or version are presumably know about --help and > --version; they aren't exactly GHC-specific! GHCi is the only executable thing (i.e., not just a document) that gets added to the start menu when someone downloads and installs GHC for Windows. If it were changed so that they just see "Prelude>" when they click on it, I'm afraid it would make Haskell seem quite unfriendly indeed! -- Chris Smith From ndmitchell at gmail.com Fri Jun 1 10:29:13 2007 From: ndmitchell at gmail.com (Neil Mitchell) Date: Fri Jun 1 10:24:53 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <46602476.8080303@gmail.com> References: <46602476.8080303@gmail.com> Message-ID: <404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com> Hi > Regarding the patch itself, I'd rather just kill the current banner and replace > it with a shorter banner if we're going to do this. What does everyone else think? Finally! Precious screen real estate should be used to give useful information, not ASCII art branding whose time has come and gone. GuiHaskell/WinHaskell have removed the banner from the very beginning. They just print out: Loading GHCi.... Prelude> Having the URL of the project home page might be handy, but a logo isn't. [1] http://www-users.cs.york.ac.uk/~ndm/guihaskell/ [2] http://www-users.cs.york.ac.uk/~ndm/winhaskell/ Thanks Neil From dons at cse.unsw.edu.au Fri Jun 1 10:32:00 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 10:28:12 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com> References: <46602476.8080303@gmail.com> <404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com> Message-ID: <20070601143200.GA3698@cse.unsw.EDU.AU> ndmitchell: > Hi > > >Regarding the patch itself, I'd rather just kill the current banner and > >replace > >it with a shorter banner if we're going to do this. What does everyone > >else think? > > Finally! Precious screen real estate should be used to give useful > information, not ASCII art branding whose time has come and gone. > GuiHaskell/WinHaskell have removed the banner from the very beginning. > They just print out: > > Loading GHCi.... > Prelude> > > Having the URL of the project home page might be handy, but a logo isn't. > > [1] http://www-users.cs.york.ac.uk/~ndm/guihaskell/ > [2] http://www-users.cs.york.ac.uk/~ndm/winhaskell/ > > Thanks $ which ghci ghci: aliased to ghci -v0 $ ghci Prelude> 1+2 3 Do we really need a patch for this? -- Don From simonmarhaskell at gmail.com Fri Jun 1 10:46:23 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Fri Jun 1 10:42:08 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <20070601143200.GA3698@cse.unsw.EDU.AU> References: <46602476.8080303@gmail.com> <404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com> <20070601143200.GA3698@cse.unsw.EDU.AU> Message-ID: <4660313F.6070502@gmail.com> Donald Bruce Stewart wrote: > ndmitchell: >> Hi >> >>> Regarding the patch itself, I'd rather just kill the current banner and >>> replace >>> it with a shorter banner if we're going to do this. What does everyone >>> else think? >> Finally! Precious screen real estate should be used to give useful >> information, not ASCII art branding whose time has come and gone. >> GuiHaskell/WinHaskell have removed the banner from the very beginning. >> They just print out: >> >> Loading GHCi.... >> Prelude> >> >> Having the URL of the project home page might be handy, but a logo isn't. >> >> [1] http://www-users.cs.york.ac.uk/~ndm/guihaskell/ >> [2] http://www-users.cs.york.ac.uk/~ndm/winhaskell/ >> >> Thanks > > > $ which ghci > ghci: aliased to ghci -v0 > > $ ghci > Prelude> 1+2 > 3 > > Do we really need a patch for this? -v0 does more than just suppress the banner, it eliminates the "Compiling" messages amongst other things. Cheers, Simon From simonmarhaskell at gmail.com Fri Jun 1 11:32:58 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Fri Jun 1 11:28:42 2007 Subject: Suggestion re altering the build system In-Reply-To: <465F6547.5040705@cse.unsw.edu.au> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> Message-ID: <46603C2A.8090703@gmail.com> Manuel M T Chakravarty wrote: > Simon Marlow wrote, >> Simon Peyton-Jones wrote: >>> | I understand that incremental builds are more tricky, but during >>> | teaching session I often have only 2 hours to hack on a day. >>> >>> I'm still hopeful that a "last-good-build" date or >>> signature-of-some-kind should do the job. Ideally it goes like this >>> >>> * Look at GHC dev wiki, get last-good-build signature >>> * darcs pull -a -upto sig >>> * make >>> >>> I'm thinking that "sig" could be a date-and-time, which you >>> copy/paste from the wiki into the darcs command. >>> >>> Or am I being naive? >> >> date/time doesn't work well with darcs. Consider the case where we >> have a successful build on date T, and then someone sent us a patch P >> that they recorded before T. We push the patch, and now "all the >> patches up to date T" includes P, but it didn't when we did the >> build. This is why we need full tags or contexts to identify the >> contents of the tree. > > Yes, it has to be tags. And it need to be tags that are in the ghc repo > *and* all core packages. (As those not being in sync is a common problem.) Not to let this dangle unsolved, let's review the options, with a few further thoughts: 1. We tag all the repos after a successful bootstrap on each platform. Main problem with this: profusion of tags, obscuring 'darcs changes' and 'darcs query tags'. Space itself isn't really an issue; a tag only adds a few hundred bytes. We could mitigate the effect by rate-limiting the tags, say only tag if there hasn't been a tag in the last week. Then we'd get one guaranteed-buildable state per week or so, which seems reasonable. 2. We keep a separate set of repos that are only updated after a successful build. Perhaps one set of repos per platform. Main problem with this: ensuring atomicity during the update (probably not likely to be a significant problem in practice). Second problem: this doesn't store the repo state of every successful build, only the most recent one. Personally I lean towards (2), as it's much easier to implement. Any further comments? Cheers, Simon From cdsmith at twu.net Fri Jun 1 11:33:32 2007 From: cdsmith at twu.net (Chris Smith) Date: Fri Jun 1 11:31:18 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup References: <46602476.8080303@gmail.com><404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com><20070601143200.GA3698@cse.unsw.EDU.AU> <4660313F.6070502@gmail.com> Message-ID: <01bb01c7a462$370a2330$6700a8c0@KYA> Simon Marlow wrote: > -v0 does more than just suppress the banner, it eliminates the > "Compiling" messages amongst other things. So the question is whether anyone might want to see those, but be opposed to seeing the startup banner. For what reason would someone want to see something like: Loading package base ... linking ... done. Loading package old-locale-1.0 ... linking ... done. Loading package old-time-1.0 ... linking ... done. Loading package directory-1.0 ... linking ... done. Loading package process-1.0 ... linking ... done. Loading package goa-3.0 ... linking ... done. but not want the startup banner? The other possibly relevant thing -v0 does is suppress the prompt unless stdin is a tty. I don't know enough about the tty stuff to know if this is a problem. Neil, would this be a problem for your GuiHaskell project if it used -v0, since it must do something like forking GHCi with stdin set to a pipe or named socket? That wouldn't be a tty, right? -- Chris Smith From ndmitchell at gmail.com Fri Jun 1 11:53:33 2007 From: ndmitchell at gmail.com (Neil Mitchell) Date: Fri Jun 1 11:49:12 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <01bb01c7a462$370a2330$6700a8c0@KYA> References: <46602476.8080303@gmail.com> <404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com> <20070601143200.GA3698@cse.unsw.EDU.AU> <4660313F.6070502@gmail.com> <01bb01c7a462$370a2330$6700a8c0@KYA> Message-ID: <404396ef0706010853l7d741c68i5c6cd021de91be6@mail.gmail.com> Hi Chris, > The other possibly relevant thing -v0 does is suppress the prompt unless > stdin is a tty. I don't know enough about the tty stuff to know if this is > a problem. Neil, would this be a problem for your GuiHaskell project if it > used -v0, since it must do something like forking GHCi with stdin set to a > pipe or named socket? Its entirely irrelevant, GuiHaskell already plays with the output from GHCi in fairly intimate ways - its not going to pass -v0 but it might opt to not display things to the user. Thanks Neil From simonmar at microsoft.com Fri Jun 1 12:08:05 2007 From: simonmar at microsoft.com (Simon Marlow) Date: Fri Jun 1 12:03:44 2007 Subject: patch applied (ghc): FIX #1110: the linker also needs the workaround Message-ID: <20070601160805.GA2112@cvs.haskell.org> Fri Jun 1 08:19:32 PDT 2007 Simon Marlow * FIX #1110: the linker also needs the workaround M ./compiler/main/SysTools.lhs -1 +3 From simonpj at microsoft.com Fri Jun 1 12:09:23 2007 From: simonpj at microsoft.com (Simon Peyton-Jones) Date: Fri Jun 1 12:05:05 2007 Subject: Suggestion re altering the build system In-Reply-To: <46603C2A.8090703@gmail.com> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> Message-ID: | 1. We tag all the repos after a successful bootstrap on each platform. | Main problem with this: profusion of tags, obscuring 'darcs changes' | and 'darcs query tags'. Space itself isn't really an issue; a tag | only adds a few hundred bytes. | | We could mitigate the effect by rate-limiting the tags, say only tag if | there hasn't been a tag in the last week. Then we'd get one | guaranteed-buildable state per week or so, which seems reasonable. | | 2. We keep a separate set of repos that are only updated after a successful | build. Perhaps one set of repos per platform. | Main problem with this: ensuring atomicity during the update (probably | not likely to be a significant problem in practice). | Second problem: this doesn't store the repo state of every successful | build, only the most recent one. | | Personally I lean towards (2), as it's much easier to implement. Any further | comments? (2) seems good to me. Furthermore, if we published Last good build is at repo http://darcs.haskell.org/ghc-2007-02-09 (so the date is in the repo name), and refrain from publishing until the repo is really there, there'd be no atomicity issues would there? (We can just delete older ones after a bit.) Simon From isaacdupree at charter.net Fri Jun 1 15:29:52 2007 From: isaacdupree at charter.net (Isaac Dupree) Date: Fri Jun 1 15:24:04 2007 Subject: darcs patch: FIX #1378 Add option for a shorter banner on GHCi startup In-Reply-To: <01bb01c7a462$370a2330$6700a8c0@KYA> References: <46602476.8080303@gmail.com><404396ef0706010729q2e4fb6f5hae894584d2556d0e@mail.gmail.com><20070601143200.GA3698@cse.unsw.EDU.AU> <4660313F.6070502@gmail.com> <01bb01c7a462$370a2330$6700a8c0@KYA> Message-ID: <466073B0.3020803@charter.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Smith wrote: > Simon Marlow wrote: >> -v0 does more than just suppress the banner, it eliminates the >> "Compiling" messages amongst other things. > > So the question is whether anyone might want to see those, but be > opposed to seeing the startup banner. For what reason would someone > want to see something like: > > Loading package base ... linking ... done. > Loading package old-locale-1.0 ... linking ... done. > Loading package old-time-1.0 ... linking ... done. > Loading package directory-1.0 ... linking ... done. > Loading package process-1.0 ... linking ... done. > Loading package goa-3.0 ... linking ... done. > > but not want the startup banner? I want to see what packages GHCi is loading when, for my information and because it generally takes a little time so I'd like to know what it's doing. (note that packages can be loaded later on, too, not just when ghci starts up) Whereas I don't want my (personal) time wasted with a distracting banner - not even if I want higher-than-normal verbosity for debugging purposes. Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGYHOvHgcxvIWYTTURAsouAKDYX72i6PbfZVWFOwC8gCRLD2D7NACfd+i5 TIjDFH6AmfEobecPGs/ggLI= =MbhT -----END PGP SIGNATURE----- From ghcbuild at microsoft.com Fri Jun 1 16:03:29 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Fri Jun 1 16:03:31 2007 Subject: [nightly] 01-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070601200329.840C5324533@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Fri Jun 1 19:30:00 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070601) **** Building stage 1 compiler ... failed; relevant barfage is below. No successfully built compilers to test; aborting. ------------------------------------------------------------------------ ------------------------------------------------------------------------ The last 30 lines of /playpen/ghc/nightly/HEAD-cam-02-unx/logs/i386-unknown-linux-stage1 are ------------------------------------------------------------------------ ------------------------------------------------------------------------ configure: Compiler flavor: GHC configure: Compiler version: 6.7.20070601 configure: Using package tool: ../../utils/ghc-pkg/ghc-pkg-inplace configure: Using ar found on system at: /usr/bin/ar configure: Using haddock found on system at: /home/simonmar/fp/bin/i386-unknown-linux/haddock configure: Using ld given by user at: /usr/bin/ld configure: No pfesetup found configure: Using ranlib found on system at: /usr/bin/ranlib configure: Using runghc found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runghc configure: Using runhugs found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runhugs configure: Using tar found on system at: /bin/tar configure: Using happy: /home/simonmar/fp/bin/i386-unknown-linux/happy configure: Using alex: /home/simonmar/fp/bin/i386-unknown-linux/alex configure: Using hsc2hs: ../../utils/hsc2hs/hsc2hs-inplace configure: No c2hs found configure: No cpphs found configure: No greencard found ifBuildable/ifBuildable network setup/Setup build \ --ghc-option=-H32m --ghc-option=-O --ghc-option=-fvia-C --ghc-option=-dcore-lint Socket.hsc: In function `main': Socket.hsc:2090: `AI_ADDRCONFIG' undeclared (first use in this function) Socket.hsc:2090: (Each undeclared identifier is reported only once Socket.hsc:2090: for each function it appears in.) compiling dist/build/Network/Socket_hsc_make.c failed command was: gcc -c -D__GLASGOW_HASKELL__=607 -I/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/includes -Iinclude -DCALLCONV=ccall dist/build/Network/Socket_hsc_make.c -o dist/build/Network/Socket_hsc_make.o Reading parameters from /playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries/network/network.buildinfo Preprocessing library network-2.0.1... gmake[1]: *** [build.library.network] Error 1 gmake[1]: Leaving directory `/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries' gmake: *** [stage1] Error 2 Nightly run ended at Fri Jun 1 21:07:48 BST 2007 From isaacdupree at charter.net Fri Jun 1 17:06:53 2007 From: isaacdupree at charter.net (Isaac Dupree) Date: Fri Jun 1 17:02:31 2007 Subject: patch applied (ghc): implement FastMutInt in non-GHC using IORefs (#1405) Message-ID: <20070601210653.GA14757@cvs.haskell.org> Fri Jun 1 13:49:48 PDT 2007 Isaac Dupree * implement FastMutInt in non-GHC using IORefs (#1405) ghc still works, also the module was tested in hugs and ghc M ./compiler/utils/FastMutInt.lhs -5 +30 From stefanor at cox.net Fri Jun 1 18:36:33 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Fri Jun 1 18:32:13 2007 Subject: Suggestion re altering the build system In-Reply-To: References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> Message-ID: <20070601223633.GA2931@localhost.localdomain> On Fri, Jun 01, 2007 at 05:09:23PM +0100, Simon Peyton-Jones wrote: > | 1. We tag all the repos after a successful bootstrap on each platform. > | Main problem with this: profusion of tags, obscuring 'darcs changes' > | and 'darcs query tags'. Space itself isn't really an issue; a tag > | only adds a few hundred bytes. > | > | We could mitigate the effect by rate-limiting the tags, say only tag if > | there hasn't been a tag in the last week. Then we'd get one > | guaranteed-buildable state per week or so, which seems reasonable. > | > | 2. We keep a separate set of repos that are only updated after a successful > | build. Perhaps one set of repos per platform. > | Main problem with this: ensuring atomicity during the update (probably > | not likely to be a significant problem in practice). > | Second problem: this doesn't store the repo state of every successful > | build, only the most recent one. > | > | Personally I lean towards (2), as it's much easier to implement. Any further > | comments? > > (2) seems good to me. Furthermore, if we published > Last good build is at repo http://darcs.haskell.org/ghc-2007-02-09 > (so the date is in the repo name), and refrain from publishing until the repo is really there, there'd be no atomicity issues would there? > > (We can just delete older ones after a bit.) 3 (mentioned earlier): Like 1, but don't push the tags. Instead we darcs send -o them and publish. The workflow for a checkout is: darcs get /my/local/fullghc/repo /ghc/build/path cd /ghc/build/path wget http://url/of/latest-tag darcs apply latest-tag darcs unpull --from-tag=BUILDS This has the space/network usage of (1) and the infrastructure ease of (2). Stefan From cvs-ghc at haskell.org Sat Jun 2 03:30:02 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Sat Jun 2 03:25:39 2007 Subject: Daily report for head Message-ID: <200706020730.l527U2QF031990@monk.galois.com> Build results: x86-64 Linux head: fail (failed boot) x86 Windows head: fail (failed stage1) x86 Windows head fast: pass pass fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) x86-64 Linux head unreg: fail (failed boot) Old unexpected test passes: arith008 1 x86 Windows head Old unexpected test failures: GMapAssoc 1 x86 Windows head GMapTop 1 x86 Windows head TH_exn2 1 x86 Windows head fast arith005 1 x86 Windows head arith008 1 x86 Windows head arith011 2 x86 Windows head arith012 1 x86 Windows head barton-mangler-bug 1 x86 Windows head base01 1 x86 Windows head break014 2 x86 Windows head break015 2 x86 Windows head break017 2 x86 Windows head cg002 1 x86 Windows head conc023 1 x86 Windows head conc052 1 x86 Windows head conc057 1 x86 Windows head conc063 1 x86 Windows head drv006 1 x86 Windows head drv008 1 x86 Windows head drv009 1 x86 Windows head drvfail001 2 x86 Windows head drvfail002 2 x86 Windows head drvfail003 2 x86 Windows head drvfail007 2 x86 Windows head dynbrk005 2 x86 Windows head ffi-deriv1 2 x86 Windows head ffi009 1 x86 Windows head gadt23 1 x86 Windows head galois_raytrace 1 x86 Windows head getC 2 x86 Windows head getDirContents001 1 x86 Windows head ghc-e001 2 x86 Windows head ghciprog004 1 x86 Windows head fast haddock.Test 1 x86 Windows head ind2 1 x86 Windows head list001 2 x86 Windows head maessen_hashtab 1 x86 Windows head net001 1 x86 Windows head num012 1 x86 Windows head par001 1 x86 Windows head pkg01 1 x86 Windows head prog003 2 x86 Windows head read008 2 x86 Windows head read016 1 x86 Windows head read025 1 x86 Windows head read040 2 x86 Windows head readwrite002 2 x86 Windows head result001 2 x86 Windows head rn019 1 x86 Windows head rn025 1 x86 Windows head rn026 1 x86 Windows head rn027 1 x86 Windows head rn028 1 x86 Windows head rn029 1 x86 Windows head rn031 1 x86 Windows head rn032 1 x86 Windows head rn033 1 x86 Windows head rn037 1 x86 Windows head rn046 1 x86 Windows head rnfail028 2 x86 Windows head simpl004 1 x86 Windows head simpl007 1 x86 Windows head simplCore.prog002 1 x86 Windows head tc049 2 x86 Windows head tc080 1 x86 Windows head tc127 1 x86 Windows head tcfail046 2 x86 Windows head tcfail072 2 x86 Windows head tcfail105 2 x86 Windows head tcfail118 2 x86 Windows head tcfail140 2 x86 Windows head tcfail145 2 x86 Windows head tcfail169 2 x86 Windows head tcfail177 2 x86 Windows head tcrun022 1 x86 Windows head typecheck.testeq1 1 x86 Windows head -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 -------------- next part -------------- Last 30 lines: .\Network\BSD.hsc:136:25: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:171:20: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:196:24: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:329:22: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:330:23: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:372:17: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:528:18: Not in scope: type constructor or class `HostName' <> Reading parameters from c:\builds\slave\x86-win-head\build\libraries\network\network.buildinfo Preprocessing library network-2.0.1... Building network-2.0.1... make[2]: *** [build.library.network] Error 1 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: rm: cannot remove directory `C:\\builds\\slave/x86-win-fast-head/build/compiler': Device or resource busy -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 From ghcbuild at microsoft.com Sat Jun 2 16:02:22 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Sat Jun 2 16:02:24 2007 Subject: [nightly] 02-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070602200222.A3BF23244A6@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Sat Jun 2 19:30:00 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070602) **** Building stage 1 compiler ... failed; relevant barfage is below. No successfully built compilers to test; aborting. ------------------------------------------------------------------------ ------------------------------------------------------------------------ The last 30 lines of /playpen/ghc/nightly/HEAD-cam-02-unx/logs/i386-unknown-linux-stage1 are ------------------------------------------------------------------------ ------------------------------------------------------------------------ configure: Compiler flavor: GHC configure: Compiler version: 6.7.20070602 configure: Using package tool: ../../utils/ghc-pkg/ghc-pkg-inplace configure: Using ar found on system at: /usr/bin/ar configure: Using haddock found on system at: /home/simonmar/fp/bin/i386-unknown-linux/haddock configure: Using ld given by user at: /usr/bin/ld configure: No pfesetup found configure: Using ranlib found on system at: /usr/bin/ranlib configure: Using runghc found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runghc configure: Using runhugs found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runhugs configure: Using tar found on system at: /bin/tar configure: Using happy: /home/simonmar/fp/bin/i386-unknown-linux/happy configure: Using alex: /home/simonmar/fp/bin/i386-unknown-linux/alex configure: Using hsc2hs: ../../utils/hsc2hs/hsc2hs-inplace configure: No c2hs found configure: No cpphs found configure: No greencard found ifBuildable/ifBuildable network setup/Setup build \ --ghc-option=-H32m --ghc-option=-O --ghc-option=-fvia-C --ghc-option=-dcore-lint Socket.hsc: In function `main': Socket.hsc:2090: `AI_ADDRCONFIG' undeclared (first use in this function) Socket.hsc:2090: (Each undeclared identifier is reported only once Socket.hsc:2090: for each function it appears in.) compiling dist/build/Network/Socket_hsc_make.c failed command was: gcc -c -D__GLASGOW_HASKELL__=607 -I/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/includes -Iinclude -DCALLCONV=ccall dist/build/Network/Socket_hsc_make.c -o dist/build/Network/Socket_hsc_make.o Reading parameters from /playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries/network/network.buildinfo Preprocessing library network-2.0.1... gmake[1]: *** [build.library.network] Error 1 gmake[1]: Leaving directory `/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries' gmake: *** [stage1] Error 2 Nightly run ended at Sat Jun 2 21:06:45 BST 2007 From cvs-ghc at haskell.org Sun Jun 3 03:30:01 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Sun Jun 3 03:25:38 2007 Subject: Daily report for head Message-ID: <200706030730.l537U1BF008431@monk.galois.com> Build results: x86-64 Linux head: fail (failed boot) x86 Windows head: fail (failed stage1) x86 Windows head fast: fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) x86-64 Linux head unreg: fail (failed boot) Old unexpected test passes: arith008 1 x86 Windows head Old unexpected test failures: GMapAssoc 1 x86 Windows head GMapTop 1 x86 Windows head TH_exn2 1 x86 Windows head fast arith005 1 x86 Windows head arith008 1 x86 Windows head arith011 2 x86 Windows head arith012 1 x86 Windows head barton-mangler-bug 1 x86 Windows head base01 1 x86 Windows head break014 2 x86 Windows head break015 2 x86 Windows head break017 2 x86 Windows head cg002 1 x86 Windows head conc023 1 x86 Windows head conc052 1 x86 Windows head conc057 1 x86 Windows head conc063 1 x86 Windows head drv006 1 x86 Windows head drv008 1 x86 Windows head drv009 1 x86 Windows head drvfail001 2 x86 Windows head drvfail002 2 x86 Windows head drvfail003 2 x86 Windows head drvfail007 2 x86 Windows head dynbrk005 2 x86 Windows head ffi-deriv1 2 x86 Windows head ffi009 1 x86 Windows head gadt23 1 x86 Windows head galois_raytrace 1 x86 Windows head getC 2 x86 Windows head getDirContents001 1 x86 Windows head ghc-e001 2 x86 Windows head ghciprog004 1 x86 Windows head fast haddock.Test 1 x86 Windows head ind2 1 x86 Windows head list001 2 x86 Windows head maessen_hashtab 1 x86 Windows head net001 1 x86 Windows head num012 1 x86 Windows head par001 1 x86 Windows head pkg01 1 x86 Windows head prog003 2 x86 Windows head read008 2 x86 Windows head read016 1 x86 Windows head read025 1 x86 Windows head read040 2 x86 Windows head readwrite002 2 x86 Windows head result001 2 x86 Windows head rn019 1 x86 Windows head rn025 1 x86 Windows head rn026 1 x86 Windows head rn027 1 x86 Windows head rn028 1 x86 Windows head rn029 1 x86 Windows head rn031 1 x86 Windows head rn032 1 x86 Windows head rn033 1 x86 Windows head rn037 1 x86 Windows head rn046 1 x86 Windows head rnfail028 2 x86 Windows head simpl004 1 x86 Windows head simpl007 1 x86 Windows head simplCore.prog002 1 x86 Windows head tc049 2 x86 Windows head tc080 1 x86 Windows head tc127 1 x86 Windows head tcfail046 2 x86 Windows head tcfail072 2 x86 Windows head tcfail105 2 x86 Windows head tcfail118 2 x86 Windows head tcfail140 2 x86 Windows head tcfail145 2 x86 Windows head tcfail169 2 x86 Windows head tcfail177 2 x86 Windows head tcrun022 1 x86 Windows head typecheck.testeq1 1 x86 Windows head -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 -------------- next part -------------- Last 30 lines: .\Network\BSD.hsc:136:25: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:171:20: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:196:24: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:329:22: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:330:23: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:372:17: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:528:18: Not in scope: type constructor or class `HostName' <> Reading parameters from c:\builds\slave\x86-win-head\build\libraries\network\network.buildinfo Preprocessing library network-2.0.1... Building network-2.0.1... make[2]: *** [build.library.network] Error 1 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: rm: cannot remove directory `C:\\builds\\slave/x86-win-fast-head/build/compiler': Device or resource busy -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 From ghcbuild at microsoft.com Sun Jun 3 16:02:19 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Sun Jun 3 16:02:21 2007 Subject: [nightly] 03-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070603200219.58983324117@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Sun Jun 3 19:30:00 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070603) **** Building stage 1 compiler ... failed; relevant barfage is below. No successfully built compilers to test; aborting. ------------------------------------------------------------------------ ------------------------------------------------------------------------ The last 30 lines of /playpen/ghc/nightly/HEAD-cam-02-unx/logs/i386-unknown-linux-stage1 are ------------------------------------------------------------------------ ------------------------------------------------------------------------ configure: Compiler flavor: GHC configure: Compiler version: 6.7.20070603 configure: Using package tool: ../../utils/ghc-pkg/ghc-pkg-inplace configure: Using ar found on system at: /usr/bin/ar configure: Using haddock found on system at: /home/simonmar/fp/bin/i386-unknown-linux/haddock configure: Using ld given by user at: /usr/bin/ld configure: No pfesetup found configure: Using ranlib found on system at: /usr/bin/ranlib configure: Using runghc found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runghc configure: Using runhugs found on system at: /home/simonmar/fp/bin/i386-unknown-linux/runhugs configure: Using tar found on system at: /bin/tar configure: Using happy: /home/simonmar/fp/bin/i386-unknown-linux/happy configure: Using alex: /home/simonmar/fp/bin/i386-unknown-linux/alex configure: Using hsc2hs: ../../utils/hsc2hs/hsc2hs-inplace configure: No c2hs found configure: No cpphs found configure: No greencard found ifBuildable/ifBuildable network setup/Setup build \ --ghc-option=-H32m --ghc-option=-O --ghc-option=-fvia-C --ghc-option=-dcore-lint Socket.hsc: In function `main': Socket.hsc:2090: `AI_ADDRCONFIG' undeclared (first use in this function) Socket.hsc:2090: (Each undeclared identifier is reported only once Socket.hsc:2090: for each function it appears in.) compiling dist/build/Network/Socket_hsc_make.c failed command was: gcc -c -D__GLASGOW_HASKELL__=607 -I/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/includes -Iinclude -DCALLCONV=ccall dist/build/Network/Socket_hsc_make.c -o dist/build/Network/Socket_hsc_make.o Reading parameters from /playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries/network/network.buildinfo Preprocessing library network-2.0.1... gmake[1]: *** [build.library.network] Error 1 gmake[1]: Leaving directory `/playpen/ghc/nightly/HEAD-cam-02-unx/i386-unknown-linux/libraries' gmake: *** [stage1] Error 2 Nightly run ended at Sun Jun 3 21:06:45 BST 2007 From isaacdupree at charter.net Sun Jun 3 17:59:34 2007 From: isaacdupree at charter.net (Isaac Dupree) Date: Sun Jun 3 17:53:34 2007 Subject: how to check for performance regressions caused by ghc hacking? Message-ID: <466339C6.1090906@charter.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While working on making GHC more compilable by other compilers, and seeing some code that would be nicer-looking refactored anyway: I want to change the code, but I'm afraid I'll make GHC's speed worse (these are critical things like FastString and FiniteMap). I could send my patches to the list, but would the reviewers know any better than me just by looking at it? (I'm much better at mental strictness/sharing/etc. analysis than I used to be, at least) ... so, what's a good way to observe the overall speed that a GHC compiles things at? (Is or should this be somewhere in the GHC Commentary? I didn't find anything relevant there) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGYznFHgcxvIWYTTURAiXbAJsEBstvLehNg68VK6i+1q9FdxhjygCgi6oH EfdDIUMIZR12EwVxgUagvzg= =iM3D -----END PGP SIGNATURE----- From stefanor at cox.net Sun Jun 3 18:14:47 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Sun Jun 3 18:10:20 2007 Subject: how to check for performance regressions caused by ghc hacking? In-Reply-To: <466339C6.1090906@charter.net> References: <466339C6.1090906@charter.net> Message-ID: <20070603221447.GA7001@localhost.localdomain> On Sun, Jun 03, 2007 at 05:59:34PM -0400, Isaac Dupree wrote: > Hash: SHA1 > > While working on making GHC more compilable by other compilers, and > seeing some code that would be nicer-looking refactored anyway: I want > to change the code, but I'm afraid I'll make GHC's speed worse (these > are critical things like FastString and FiniteMap). I could send my > patches to the list, but would the reviewers know any better than me > just by looking at it? (I'm much better at mental > strictness/sharing/etc. analysis than I used to be, at least) ... so, > what's a good way to observe the overall speed that a GHC compiles > things at? (Is or should this be somewhere in the GHC Commentary? I > didn't find anything relevant there) We already have a Haskell runtime performance testing suite: http://www.cse.unsw.edu.au/~dons/code/nobench Extending it to measure compile times shouldn't be hard. Note that you'll have to set up your own instance, because the public instance won't have ghc-isaacd. (Of course, compile time measurement patches should be sent upstream) Stefan From cvs-ghc at haskell.org Mon Jun 4 03:30:01 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Mon Jun 4 03:25:31 2007 Subject: Daily report for head Message-ID: <200706040730.l547U1YX003779@monk.galois.com> Build results: x86-64 Linux head: fail (failed boot) x86 Windows head: fail (failed stage1) x86 Windows head fast: fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) fail (failed darcs) x86-64 Linux head unreg: fail (failed boot) Old unexpected test passes: arith008 1 x86 Windows head Old unexpected test failures: GMapAssoc 1 x86 Windows head GMapTop 1 x86 Windows head TH_exn2 1 x86 Windows head fast arith005 1 x86 Windows head arith008 1 x86 Windows head arith011 2 x86 Windows head arith012 1 x86 Windows head barton-mangler-bug 1 x86 Windows head base01 1 x86 Windows head break014 2 x86 Windows head break015 2 x86 Windows head break017 2 x86 Windows head cg002 1 x86 Windows head conc023 1 x86 Windows head conc052 1 x86 Windows head conc057 1 x86 Windows head conc063 1 x86 Windows head drv006 1 x86 Windows head drv008 1 x86 Windows head drv009 1 x86 Windows head drvfail001 2 x86 Windows head drvfail002 2 x86 Windows head drvfail003 2 x86 Windows head drvfail007 2 x86 Windows head dynbrk005 2 x86 Windows head ffi-deriv1 2 x86 Windows head ffi009 1 x86 Windows head gadt23 1 x86 Windows head galois_raytrace 1 x86 Windows head getC 2 x86 Windows head getDirContents001 1 x86 Windows head ghc-e001 2 x86 Windows head ghciprog004 1 x86 Windows head fast haddock.Test 1 x86 Windows head ind2 1 x86 Windows head list001 2 x86 Windows head maessen_hashtab 1 x86 Windows head net001 1 x86 Windows head num012 1 x86 Windows head par001 1 x86 Windows head pkg01 1 x86 Windows head prog003 2 x86 Windows head read008 2 x86 Windows head read016 1 x86 Windows head read025 1 x86 Windows head read040 2 x86 Windows head readwrite002 2 x86 Windows head result001 2 x86 Windows head rn019 1 x86 Windows head rn025 1 x86 Windows head rn026 1 x86 Windows head rn027 1 x86 Windows head rn028 1 x86 Windows head rn029 1 x86 Windows head rn031 1 x86 Windows head rn032 1 x86 Windows head rn033 1 x86 Windows head rn037 1 x86 Windows head rn046 1 x86 Windows head rnfail028 2 x86 Windows head simpl004 1 x86 Windows head simpl007 1 x86 Windows head simplCore.prog002 1 x86 Windows head tc049 2 x86 Windows head tc080 1 x86 Windows head tc127 1 x86 Windows head tcfail046 2 x86 Windows head tcfail072 2 x86 Windows head tcfail105 2 x86 Windows head tcfail118 2 x86 Windows head tcfail140 2 x86 Windows head tcfail145 2 x86 Windows head tcfail169 2 x86 Windows head tcfail177 2 x86 Windows head tcrun022 1 x86 Windows head typecheck.testeq1 1 x86 Windows head -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 -------------- next part -------------- Last 30 lines: .\Network\BSD.hsc:136:25: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:171:20: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:196:24: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:329:22: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:330:23: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:372:17: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:528:18: Not in scope: type constructor or class `HostName' <> Reading parameters from c:\builds\slave\x86-win-head\build\libraries\network\network.buildinfo Preprocessing library network-2.0.1... Building network-2.0.1... make[2]: *** [build.library.network] Error 1 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: rm: cannot remove directory `C:\\builds\\slave/x86-win-fast-head/build/compiler': Device or resource busy -------------- next part -------------- Last 30 lines: Booting . Booting libraries/ALUT Booting libraries/GLUT Booting libraries/HGL Booting libraries/OpenAL Booting libraries/OpenGL Booting libraries/Win32 Booting libraries/X11 Booting libraries/base Booting libraries/directory autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 From simonmarhaskell at gmail.com Mon Jun 4 04:05:55 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Mon Jun 4 04:01:28 2007 Subject: Suggestion re altering the build system In-Reply-To: <20070601223633.GA2931@localhost.localdomain> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> <20070601223633.GA2931@localhost.localdomain> Message-ID: <4663C7E3.9040800@gmail.com> Stefan O'Rear wrote: > On Fri, Jun 01, 2007 at 05:09:23PM +0100, Simon Peyton-Jones wrote: >> | 1. We tag all the repos after a successful bootstrap on each platform. >> | Main problem with this: profusion of tags, obscuring 'darcs changes' >> | and 'darcs query tags'. Space itself isn't really an issue; a tag >> | only adds a few hundred bytes. >> | >> | We could mitigate the effect by rate-limiting the tags, say only tag if >> | there hasn't been a tag in the last week. Then we'd get one >> | guaranteed-buildable state per week or so, which seems reasonable. >> | >> | 2. We keep a separate set of repos that are only updated after a successful >> | build. Perhaps one set of repos per platform. >> | Main problem with this: ensuring atomicity during the update (probably >> | not likely to be a significant problem in practice). >> | Second problem: this doesn't store the repo state of every successful >> | build, only the most recent one. >> | >> | Personally I lean towards (2), as it's much easier to implement. Any further >> | comments? >> >> (2) seems good to me. Furthermore, if we published >> Last good build is at repo http://darcs.haskell.org/ghc-2007-02-09 >> (so the date is in the repo name), and refrain from publishing until the repo is really there, there'd be no atomicity issues would there? >> >> (We can just delete older ones after a bit.) > > 3 (mentioned earlier): Like 1, but don't push the tags. Instead we > darcs send -o them and publish. The workflow for a checkout is: > > darcs get /my/local/fullghc/repo /ghc/build/path > cd /ghc/build/path > wget http://url/of/latest-tag > darcs apply latest-tag > darcs unpull --from-tag=BUILDS > > This has the space/network usage of (1) and the infrastructure ease of > (2). We talked about this idea a little on IRC, unfortunately it has two pretty serious drawbacks: - if the user's local repo has some recorded patches that aren't in the main GHC repo, they'll get unpulled too. Getting a tree from scratch is fine, but this method can't be used to update a development branch to the latest working HEAD, which was one of the goals. - the tags may appear in the context of patches that people 'darcs send', which would force us to pull the tags into the main repo (or tell people not to do that, but we don't want to add extra obstacles for contributors). Cheers, Simon From simonmarhaskell at gmail.com Mon Jun 4 04:09:06 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Mon Jun 4 04:04:39 2007 Subject: Suggestion re altering the build system In-Reply-To: References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> Message-ID: <4663C8A2.6080201@gmail.com> Simon Peyton-Jones wrote: > | 1. We tag all the repos after a successful bootstrap on each platform. > | Main problem with this: profusion of tags, obscuring 'darcs changes' > | and 'darcs query tags'. Space itself isn't really an issue; a tag > | only adds a few hundred bytes. > | > | We could mitigate the effect by rate-limiting the tags, say only tag if > | there hasn't been a tag in the last week. Then we'd get one > | guaranteed-buildable state per week or so, which seems reasonable. > | > | 2. We keep a separate set of repos that are only updated after a successful > | build. Perhaps one set of repos per platform. > | Main problem with this: ensuring atomicity during the update (probably > | not likely to be a significant problem in practice). > | Second problem: this doesn't store the repo state of every successful > | build, only the most recent one. > | > | Personally I lean towards (2), as it's much easier to implement. Any further > | comments? > > (2) seems good to me. Furthermore, if we published > Last good build is at repo http://darcs.haskell.org/ghc-2007-02-09 > (so the date is in the repo name), and refrain from publishing until the repo is really there, there'd be no atomicity issues would there? > > (We can just delete older ones after a bit.) Indeed, that's a good idea, although it's more work than just pushing. We wouldn't want to create a complete new set of repos for every successful build, I don't think. Cheers, Simon From simonmarhaskell at gmail.com Mon Jun 4 06:07:53 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Mon Jun 4 06:03:27 2007 Subject: how to check for performance regressions caused by ghc hacking? In-Reply-To: <20070603221447.GA7001@localhost.localdomain> References: <466339C6.1090906@charter.net> <20070603221447.GA7001@localhost.localdomain> Message-ID: <4663E479.9080608@gmail.com> Stefan O'Rear wrote: > On Sun, Jun 03, 2007 at 05:59:34PM -0400, Isaac Dupree wrote: >> Hash: SHA1 >> >> While working on making GHC more compilable by other compilers, and >> seeing some code that would be nicer-looking refactored anyway: I want >> to change the code, but I'm afraid I'll make GHC's speed worse (these >> are critical things like FastString and FiniteMap). I could send my >> patches to the list, but would the reviewers know any better than me >> just by looking at it? (I'm much better at mental >> strictness/sharing/etc. analysis than I used to be, at least) ... so, >> what's a good way to observe the overall speed that a GHC compiles >> things at? (Is or should this be somewhere in the GHC Commentary? I >> didn't find anything relevant there) > > We already have a Haskell runtime performance testing suite: > > http://www.cse.unsw.edu.au/~dons/code/nobench > > Extending it to measure compile times shouldn't be hard. Note that > you'll have to set up your own instance, because the public instance > won't have ghc-isaacd. > > (Of course, compile time measurement patches should be sent upstream) Right, extending nobench to do this would be great. You can also use the existing nofib suite, together with utils/nofib-analyse, to get compile times compared across two separate runs. This is pretty unreliable for measuring small changes, though. When I make a small change to the compiler, as a performance sanity check I often go and compile nofib/anna with and without the change. Something like this: $ cd nofib/anna $ ghc -O --make -cpp Main +RTS -sstderr $ ghc-new -O --make -cpp Main +RTS -sstderr note that results from this test shouldn't be considered definitive - probably compiling GHC with itself would be a better test. Cheers, Simon From bjpop at csse.unimelb.edu.au Mon Jun 4 22:13:43 2007 From: bjpop at csse.unimelb.edu.au (Bernie Pope) Date: Mon Jun 4 22:09:13 2007 Subject: patch applied (ghc): Add missing newline from ghci :help output Message-ID: <20070605021343.GA32601@cvs.haskell.org> Mon Jun 4 19:09:30 PDT 2007 bjpop@csse.unimelb.edu.au * Add missing newline from ghci :help output M ./compiler/ghci/InteractiveUI.hs -1 +1 From ghcbuild at microsoft.com Mon Jun 4 23:29:21 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Mon Jun 4 23:29:23 2007 Subject: [nightly] 04-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070605032921.74E6332415C@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Mon Jun 4 19:30:01 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070604) **** Building stage 1 compiler ... ok. **** Building stage 2 compiler ... ok. **** Building stage 3 compiler ... ok. **** building testsuite tools ... ok. **** running tests ... ok (summary below). **** building compiler binary distribution ... ok. **** generating binary distribution + manifest ... ok. **** running nofib (-O) ... ok. (2 failures) **** running nofib (-O -fasm) ... ok. (2 failures) **** running nofib (-O -prof -auto-all) ... ok. (5 failures) **** running nofib (-O -prof -auto-all -fasm) ... ok. (5 failures) **** running nofib (-fasm) ... ok. (2 failures) **** running nofib (-unreg) ... failed. **** publishing distfiles ... Read from remote host haskell.org: Connection reset by peer lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. **** publishing logs ... Read from remote host haskell.org: Connection reset by peer lost connection failed. **** publishing docs ... ok. Logs are at http://www.haskell.org/ghc/dist/current/logs Dists are at http://www.haskell.org/ghc/dist/current/dist Docs are at http://www.haskell.org/ghc/dist/current/docs All done! Nightly build finished successfully at Tue Jun 5 04:33:53 BST 2007 ------------- GHC Test summary --------------------- OVERALL SUMMARY for test run started at Mon Jun 4 22:46:52 BST 2007 1769 total tests, which gave rise to 9421 test cases, of which 18 caused framework failures 1692 were skipped 7396 expected passes 98 expected failures 2 unexpected passes 215 unexpected failures Unexpected passes: arith008(profasm) read032(normal) Unexpected failures: GMapAssoc(optc,hpc,profc,profasm) GMapTop(optc,hpc,profc,profasm) TH_exn2(normal) arith005(optc,hpc,optasm,profc,profasm,threaded2) arith008(hpc,threaded2) arith011(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) arith012(hpc,threaded2) barton-mangler-bug(profc) base01(normal) break014(ghci) break015(ghci) break016(ghci) break017(ghci) cg002(optc,profc) conc048(threaded2) conc052(profc,profasm) conc053(threaded1,threaded2) conc057(threaded2) conc063(normal,optc,hpc,optasm,profc,profasm,threaded1,threaded2) concprog001(ghci) drv006(optc,profc) drv008(optc,profc) drv009(optc,profc) drvfail001(normal) drvfail002(normal) drvfail003(normal) drvfail007(normal) dynbrk005(ghci) ffi-deriv1(normal,optc,hpc,optasm,profc,profasm) ffi009(threaded2) gadt23(normal) galois_raytrace(hpc,optasm,profasm,threaded2) getC(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ghc-e001(normal) ghci005(ghci) hGetBuf001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) haddock.Test(optc,profc) ind2(profc,profasm) maessen_hashtab(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) net001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) num012(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) par001(threaded1,threaded2) pkg01(optc,profc) prog001(ghci) prog002(ghci) prog003(ghci) read008(normal) read016(optc,profc) read025(optc,profc) read040(normal,optc,hpc,optasm,profc,profasm) result001(ghci) rn019(optc,profc) rn025(optc,profc) rn026(optc,profc) rn027(optc,profc) rn028(optc,profc) rn029(optc,profc) rn031(optc,profc) rn032(optc,profc) rn033(optc,profc) rn037(optc,profc) rn046(optc,profc) rnfail028(normal) simpl004(optc,profc) simpl007(optc,profc) simplCore.prog002(optc,profc) tc049(normal,optc,hpc,optasm,profc,profasm) tc080(optc,profc) tc127(optc,profc) tcfail046(normal) tcfail072(normal) tcfail105(normal,optc,hpc,optasm,profc,profasm) tcfail118(normal) tcfail140(normal) tcfail145(normal) tcfail169(normal) tcfail177(normal) tcrun007(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) tcrun022(ghci) user001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ---------------------------------------------------- Nightly run ended at Tue Jun 5 04:33:53 BST 2007 From cvs-ghc at haskell.org Tue Jun 5 03:30:02 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Tue Jun 5 03:25:30 2007 Subject: Daily report for head Message-ID: <200706050730.l557U2gv007393@monk.galois.com> Build results: x86-64 Linux head: lost x86 Windows head: fail (failed stage1) x86 Windows head fast: fail (failed darcs) pass pass pass pass pass x86-64 Linux head unreg: fail (failed stage1) Dropping unexpected test passes reports from builders not seen in 7 days: x86 Windows head Fixed unexpected test passes: arith008 Dropping unexpected test failures reports from builders not seen in 7 days: x86 Windows head Fixed unexpected test failures: GMapAssoc GMapTop arith005 arith008 arith012 barton-mangler-bug base01 cg002 conc023 conc052 conc057 conc063 drv006 drv008 drv009 ffi009 gadt23 galois_raytrace getDirContents001 haddock.Test ind2 maessen_hashtab net001 num012 par001 pkg01 read016 read025 rn019 rn025 rn026 rn027 rn028 rn029 rn031 rn032 rn033 rn037 rn046 simpl004 simpl007 simplCore.prog002 tc080 tc127 tcrun022 typecheck.testeq1 Old unexpected test failures: TH_exn2 1 x86 Windows head fast arith011 1 x86 Windows head fast break014 1 x86 Windows head fast break015 1 x86 Windows head fast break017 1 x86 Windows head fast drvfail001 1 x86 Windows head fast drvfail002 1 x86 Windows head fast drvfail003 1 x86 Windows head fast drvfail007 1 x86 Windows head fast dynbrk005 1 x86 Windows head fast ffi-deriv1 1 x86 Windows head fast getC 1 x86 Windows head fast ghc-e001 1 x86 Windows head fast ghciprog004 1 x86 Windows head fast list001 1 x86 Windows head fast prog003 1 x86 Windows head fast read008 1 x86 Windows head fast read040 1 x86 Windows head fast readwrite002 1 x86 Windows head fast result001 1 x86 Windows head fast rnfail028 1 x86 Windows head fast tc049 1 x86 Windows head fast tcfail046 1 x86 Windows head fast tcfail072 1 x86 Windows head fast tcfail105 1 x86 Windows head fast tcfail118 1 x86 Windows head fast tcfail140 1 x86 Windows head fast tcfail145 1 x86 Windows head fast tcfail169 1 x86 Windows head fast tcfail177 1 x86 Windows head fast -------------- next part -------------- Last 30 lines: .\Network\BSD.hsc:136:25: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:171:20: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:196:24: Not in scope: type constructor or class `ServiceName' .\Network\BSD.hsc:329:22: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:330:23: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:372:17: Not in scope: type constructor or class `HostName' .\Network\BSD.hsc:528:18: Not in scope: type constructor or class `HostName' <> Reading parameters from c:\builds\slave\x86-win-head\build\libraries\network\network.buildinfo Preprocessing library network-2.0.1... Building network-2.0.1... make[2]: *** [build.library.network] Error 1 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: [134 of 155] Compiling Data.ByteString.Lazy.Char8 ( Data/ByteString/Lazy/Char8.hs, dist/build/Data/ByteString/Lazy/Char8.p_o ) [135 of 155] Compiling GHC.TopHandler ( GHC/TopHandler.lhs, dist/build/GHC/TopHandler.p_o ) [136 of 155] Compiling System.Environment ( System/Environment.hs, dist/build/System/Environment.p_o ) [137 of 155] Compiling Control.Concurrent.MVar ( Control/Concurrent/MVar.hs, dist/build/Control/Concurrent/MVar.p_o ) [138 of 155] Compiling Control.Concurrent.QSem ( Control/Concurrent/QSem.hs, dist/build/Control/Concurrent/QSem.p_o ) [139 of 155] Compiling Control.Concurrent.QSemN ( Control/Concurrent/QSemN.hs, dist/build/Control/Concurrent/QSemN.p_o ) [140 of 155] Compiling Control.Concurrent.SampleVar ( Control/Concurrent/SampleVar.hs, dist/build/Control/Concurrent/SampleVar.p_o ) [141 of 155] Compiling Data.Array.Diff ( Data/Array/Diff.hs, dist/build/Data/Array/Diff.p_o ) [142 of 155] Compiling Data.Unique ( Data/Unique.hs, dist/build/Data/Unique.p_o ) [143 of 155] Compiling Control.Concurrent.Chan ( Control/Concurrent/Chan.hs, dist/build/Control/Concurrent/Chan.p_o ) [144 of 155] Compiling Control.Concurrent ( Control/Concurrent.hs, dist/build/Control/Concurrent.p_o ) [145 of 155] Compiling System.Timeout ( System/Timeout.hs, dist/build/System/Timeout.p_o ) [146 of 155] Compiling Control.Arrow ( Control/Arrow.hs, dist/build/Control/Arrow.p_o ) [147 of 155] Compiling Control.Applicative ( Control/Applicative.hs, dist/build/Control/Applicative.p_o ) [148 of 155] Compiling Data.Foldable ( Data/Foldable.hs, dist/build/Data/Foldable.p_o ) [149 of 155] Compiling Data.IntMap ( Data/IntMap.hs, dist/build/Data/IntMap.p_o ) [150 of 155] Compiling Data.Set ( Data/Set.hs, dist/build/Data/Set.p_o ) [151 of 155] Compiling Data.Traversable ( Data/Traversable.hs, dist/build/Data/Traversable.p_o ) [152 of 155] Compiling Data.Map ( Data/Map.hs, dist/build/Data/Map.p_o ) [153 of 155] Compiling Data.Sequence ( Data/Sequence.hs, dist/build/Data/Sequence.p_o ) [154 of 155] Compiling Data.Tree ( Data/Tree.hs, dist/build/Data/Tree.p_o ) [155 of 155] Compiling Data.Graph ( Data/Graph.hs, dist/build/Data/Graph.p_o ) <> Setup: dist/build/Control/Applicative_split: getDirectoryContents: does not exist (No such file or directory) make[2]: *** [build.library.base] Error 1 make[2]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build' From simonmar at microsoft.com Tue Jun 5 04:57:14 2007 From: simonmar at microsoft.com (Simon Marlow) Date: Tue Jun 5 04:52:42 2007 Subject: patch applied (ghc): fix panic in #1379 Message-ID: <20070605085714.GA10360@cvs.haskell.org> Tue Jun 5 01:44:38 PDT 2007 Simon Marlow * fix panic in #1379 M ./compiler/ghci/InteractiveUI.hs +4 M ./compiler/main/GHC.hs -1 +1 From eivuokko at gmail.com Tue Jun 5 07:17:13 2007 From: eivuokko at gmail.com (Esa Ilari Vuokko) Date: Tue Jun 5 07:12:42 2007 Subject: Building GHC in Windows (Was: Re: Failure in GHC compilation) Message-ID: On 6/5/07, Simon Marlow wrote: > Simon Peyton-Jones wrote: > > I've extended the "what to look for if your build fails" section in > > http://hackage.haskell.org/trac/ghc/wiki/Building/Windows > > > > Please do keep adding to this page! Every time you trip over something, think about whether your experience could be used to help someone else. > > [taken off-list] > > I'd say a bug report is a better place for this kind of thing. They're just as > searchable, and bugs can be closed more easily than editing a wiki page to > remove out-of-date text. The Windows wiki page is full of stuff that doesn't > apply any more, and IMO its size is completely daunting to anyone who wants to > build GHC on Windows. Also the fact that there are two sets of instructions > that differ in various details is confusing. Whoa, there's lots of stuff there! The page is unorganised, and I'd guess nobody wants to reorg it because nobody builds ghc in Windows more than one way, and hence, nobody knows all the little tiny bits. There's lots of choices: cygwin shell vs mingw shell; which gcc to use (cygwin, mingw, from old ghc); which stage/install method used (stage 1/2 in-place, make install, through bin-dist.) That gives easily dozen ways to build and use the resulting ghc. I've myself never (or for a long time) built ghc using cygwin, and I never managed to wrap bin-dist. I have no idea why some flags are given, like architecture-flag (iirc it works just fine without it, in msys.) Building docs required cygwin for some wierd reason I can't recall. It's not clear to me if this needs to sorted out in Wiki/other docs or if buildsystem needs thorough revision in Windows. Maybe it's all better in head (which I haven't built for a while now.) Best Regards, Esa From igloo at earth.li Tue Jun 5 11:26:53 2007 From: igloo at earth.li (Ian Lynagh) Date: Tue Jun 5 11:26:55 2007 Subject: patch applied (/haskell/ghc): Add FreeBSD x86_64 bindist Message-ID: <20070605152653.GA13862@haskell.cs.yale.edu> Tue Jun 5 11:31:05 EDT 2007 Ian Lynagh * Add FreeBSD x86_64 bindist M ./download_ghc_661.html +12 From igloo at earth.li Tue Jun 5 11:44:01 2007 From: igloo at earth.li (Ian Lynagh) Date: Tue Jun 5 11:39:28 2007 Subject: patch applied (ghc): Fix normalisation of path to find Message-ID: <20070605154401.GA27607@cvs.haskell.org> Tue Jun 5 07:50:43 PDT 2007 Ian Lynagh * Fix normalisation of path to find The old code didn't work on Mac OS X, as "which" returns successfully when it can't find the program. M ./aclocal.m4 -5 +9 From igloo at earth.li Tue Jun 5 13:49:17 2007 From: igloo at earth.li (Ian Lynagh) Date: Tue Jun 5 13:44:46 2007 Subject: patch applied (ghc): ifBuildable now prints a warning if the package is not buildable Message-ID: <20070605174917.GA32642@cvs.haskell.org> Tue Jun 5 10:47:25 PDT 2007 Ian Lynagh * ifBuildable now prints a warning if the package is not buildable M ./libraries/ifBuildable.hs -8 +14 From igloo at earth.li Tue Jun 5 15:49:03 2007 From: igloo at earth.li (Ian Lynagh) Date: Tue Jun 5 15:44:29 2007 Subject: patch applied (ghc): Typo, spotted by Stefan Holdermans Message-ID: <20070605194903.GA3622@cvs.haskell.org> Tue Jun 5 12:46:43 PDT 2007 Ian Lynagh * Typo, spotted by Stefan Holdermans M ./compiler/typecheck/TcPat.lhs -1 +1 From isaacdupree at charter.net Tue Jun 5 20:08:16 2007 From: isaacdupree at charter.net (Isaac Dupree) Date: Tue Jun 5 20:03:41 2007 Subject: patch applied (ghc): remove #if branches for pre-ghc-6.0 Message-ID: <20070606000816.GA13167@cvs.haskell.org> Tue Jun 5 16:53:01 PDT 2007 Isaac Dupree * remove #if branches for pre-ghc-6.0 I skipped utils/hsc2hs/Main.hs since its ifs also involved checking for old versions of nhc98 (I don't want to figure that out), but removed everything else I found relating to building with pre-6.0 M ./compiler/ghci/InteractiveUI.hs -4 +1 M ./compiler/main/GHC.hs -6 +1 M ./compiler/main/SysTools.lhs -8 +1 M ./compiler/utils/Binary.hs -10 M ./compiler/utils/FastString.lhs -15 +1 M ./compiler/utils/Panic.lhs -8 M ./compiler/utils/StringBuffer.lhs -15 M ./utils/genapply/GenApply.hs -9 M ./utils/ghc-pkg/Main.hs -17 From chak at cse.unsw.edu.au Tue Jun 5 21:25:07 2007 From: chak at cse.unsw.edu.au (Manuel M T Chakravarty) Date: Tue Jun 5 21:20:38 2007 Subject: Suggestion re altering the build system In-Reply-To: <4663C8A2.6080201@gmail.com> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> <4663C8A2.6080201@gmail.com> Message-ID: <46660CF3.4030805@cse.unsw.edu.au> Simon Marlow wrote: > Simon Peyton-Jones wrote: >> | 1. We tag all the repos after a successful bootstrap on each >> platform. >> | Main problem with this: profusion of tags, obscuring 'darcs >> changes' >> | and 'darcs query tags'. Space itself isn't really an issue; a tag >> | only adds a few hundred bytes. >> | >> | We could mitigate the effect by rate-limiting the tags, say >> only tag if >> | there hasn't been a tag in the last week. Then we'd get one >> | guaranteed-buildable state per week or so, which seems reasonable. >> | >> | 2. We keep a separate set of repos that are only updated after a >> successful >> | build. Perhaps one set of repos per platform. >> | Main problem with this: ensuring atomicity during the update >> (probably >> | not likely to be a significant problem in practice). >> | Second problem: this doesn't store the repo state of every >> successful >> | build, only the most recent one. >> | >> | Personally I lean towards (2), as it's much easier to implement. >> Any further >> | comments? >> >> (2) seems good to me. Furthermore, if we published >> Last good build is at repo >> http://darcs.haskell.org/ghc-2007-02-09 >> (so the date is in the repo name), and refrain from publishing until >> the repo is really there, there'd be no atomicity issues would there? >> >> (We can just delete older ones after a bit.) > > Indeed, that's a good idea, although it's more work than just pushing. > We wouldn't want to create a complete new set of repos for every > successful build, I don't think. Similar rate limiting as you proposed for (1) could be applied; ie, no more than one such repo per week. I don't quite understand why (2) is much easier to implement and having a tag a week in the main tree marking a buildable state seems quite attractive to me. Anyway, Option (2) is fine, too. However, just http://darcs.haskell.org/ghc-2007-02-09 isn't good enough. We need a consistent set of ghc repo and core packages. At least, in my experience, it's not uncommon having build problems due to ghc/ and libraries/base/ being out of sync, and at least when the build system changes, many build problems are in conjunction with packages. Manuel From ghcbuild at microsoft.com Tue Jun 5 23:17:44 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Tue Jun 5 23:17:45 2007 Subject: [nightly] 05-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070606031744.6090F32422B@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Tue Jun 5 19:30:00 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070605) **** Building stage 1 compiler ... ok. **** Building stage 2 compiler ... ok. **** Building stage 3 compiler ... ok. **** building testsuite tools ... ok. **** running tests ... ok (summary below). **** building compiler binary distribution ... ok. **** generating binary distribution + manifest ... ok. **** running nofib (-O) ... ok. (2 failures) **** running nofib (-O -fasm) ... ok. (2 failures) **** running nofib (-O -prof -auto-all) ... ok. (5 failures) **** running nofib (-O -prof -auto-all -fasm) ... ok. (5 failures) **** running nofib (-fasm) ... ok. (2 failures) **** running nofib (-unreg) ... failed. **** publishing distfiles ... Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. **** publishing logs ... ok. **** publishing docs ... ok. Logs are at http://www.haskell.org/ghc/dist/current/logs Dists are at http://www.haskell.org/ghc/dist/current/dist Docs are at http://www.haskell.org/ghc/dist/current/docs All done! Nightly build finished successfully at Wed Jun 6 04:22:19 BST 2007 ------------- GHC Test summary --------------------- OVERALL SUMMARY for test run started at Tue Jun 5 22:33:20 BST 2007 1769 total tests, which gave rise to 9421 test cases, of which 18 caused framework failures 1692 were skipped 7396 expected passes 98 expected failures 2 unexpected passes 215 unexpected failures Unexpected passes: arith008(profasm) read032(normal) Unexpected failures: GMapAssoc(optc,hpc,profc,profasm) GMapTop(optc,hpc,profc,profasm) TH_exn2(normal) arith005(optc,hpc,optasm,profc,profasm,threaded2) arith008(hpc,threaded2) arith011(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) arith012(hpc,threaded2) barton-mangler-bug(profc) base01(normal) break014(ghci) break015(ghci) break016(ghci) break017(ghci) cg002(optc,profc) conc048(threaded2) conc052(profc,profasm) conc053(threaded1,threaded2) conc057(threaded2) conc063(normal,optc,hpc,optasm,profc,profasm,threaded1,threaded2) concprog001(ghci) drv006(optc,profc) drv008(optc,profc) drv009(optc,profc) drvfail001(normal) drvfail002(normal) drvfail003(normal) drvfail007(normal) dynbrk005(ghci) ffi-deriv1(normal,optc,hpc,optasm,profc,profasm) ffi009(threaded2) gadt23(normal) galois_raytrace(hpc,optasm,profasm,threaded2) getC(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ghc-e001(normal) ghci005(ghci) hGetBuf001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) haddock.Test(optc,profc) ind2(profc,profasm) maessen_hashtab(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) net001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) num012(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) par001(threaded1,threaded2) pkg01(optc,profc) prog001(ghci) prog002(ghci) prog003(ghci) read008(normal) read016(optc,profc) read025(optc,profc) read040(normal,optc,hpc,optasm,profc,profasm) result001(ghci) rn019(optc,profc) rn025(optc,profc) rn026(optc,profc) rn027(optc,profc) rn028(optc,profc) rn029(optc,profc) rn031(optc,profc) rn032(optc,profc) rn033(optc,profc) rn037(optc,profc) rn046(optc,profc) rnfail028(normal) simpl004(optc,profc) simpl007(optc,profc) simplCore.prog002(optc,profc) tc049(normal,optc,hpc,optasm,profc,profasm) tc080(optc,profc) tc127(optc,profc) tcfail046(normal) tcfail072(normal) tcfail105(normal,optc,hpc,optasm,profc,profasm) tcfail118(normal) tcfail140(normal) tcfail145(normal) tcfail169(normal) tcfail177(normal) tcrun007(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) tcrun022(ghci) user001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ---------------------------------------------------- Nightly run ended at Wed Jun 6 04:22:19 BST 2007 From cvs-ghc at haskell.org Wed Jun 6 03:30:02 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Wed Jun 6 03:25:27 2007 Subject: Daily report for head Message-ID: <200706060730.l567U2tV022555@monk.galois.com> Build results: x86-64 Linux head: lost x86 Windows head: fail (failed bin dist) x86 Windows head fast: pass lost pass pass pass pass mnemosyne x86-64 Gentoo head: fail (failed stage1) x86-64 Linux head unreg: fail (failed stage1) New unexpected test failures: lazypat 1 x86 Windows head fast Old unexpected test failures: TH_exn2 1 x86 Windows head fast arith011 1 x86 Windows head fast break014 1 x86 Windows head fast break015 1 x86 Windows head fast break017 1 x86 Windows head fast drvfail001 1 x86 Windows head fast drvfail002 1 x86 Windows head fast drvfail003 1 x86 Windows head fast drvfail007 1 x86 Windows head fast dynbrk005 1 x86 Windows head fast ffi-deriv1 1 x86 Windows head fast getC 1 x86 Windows head fast ghc-e001 1 x86 Windows head fast ghciprog004 1 x86 Windows head fast list001 1 x86 Windows head fast prog003 1 x86 Windows head fast read008 1 x86 Windows head fast read040 1 x86 Windows head fast readwrite002 1 x86 Windows head fast result001 1 x86 Windows head fast rnfail028 1 x86 Windows head fast tc049 1 x86 Windows head fast tcfail046 1 x86 Windows head fast tcfail072 1 x86 Windows head fast tcfail105 1 x86 Windows head fast tcfail118 1 x86 Windows head fast tcfail140 1 x86 Windows head fast tcfail145 1 x86 Windows head fast tcfail169 1 x86 Windows head fast tcfail177 1 x86 Windows head fast -------------- next part -------------- Last 30 lines: ./../utils/mkdirhier/mkdirhier c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11 mkdir c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11 ifBuildable/ifBuildable X11 cp X11.cabal c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11 ifBuildable/ifBuildable X11 cp -a dist c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11 ifBuildable/ifBuildable X11 C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11/dist \ \( -name "*_split" -o -name "autogen" \) | xargs rm -rf ifBuildable/ifBuildable X11 C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/X11/dist \ \( \( -name "*.o" -o -name "*.p_o" \) -a ! -name "HS*" \) \ -exec rm {} \; ./../utils/mkdirhier/mkdirhier c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time mkdir c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time ifBuildable/ifBuildable time cp time.cabal c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time ifBuildable/ifBuildable time cp -a dist c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time ifBuildable/ifBuildable time C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time/dist \ \( -name "*_split" -o -name "autogen" \) | xargs rm -rf ifBuildable/ifBuildable time C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/time/dist \ \( \( -name "*.o" -o -name "*.p_o" \) -a ! -name "HS*" \) \ -exec rm {} \; ./../utils/mkdirhier/mkdirhier c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL mkdir c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL ifBuildable/ifBuildable OpenGL cp OpenGL.cabal c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL ifBuildable/ifBuildable OpenGL cp -a dist c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL ifBuildable/ifBuildable OpenGL C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL/dist \ \( -name "*_split" -o -name "autogen" \) | xargs rm -rf rm: cannot remove directory `c:/builds/slave/x86-win-head/build/ghc-6.7.20070605/libraries/OpenGL/dist/build/Graphics/Rendering/OpenGL/GL/Texturing/TexParameter_split': Directory not empty make[2]: *** [binary-dist.library.OpenGL] Error 123 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [binary-dist] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: unpackRLimit (18446744073709551615) = ... unpackRLimit (18446744073709551615) = ... [ 7 of 19] Compiling System.Posix.Error ( System/Posix/Error.hs, dist/build/System/Posix/Error.o ) [ 8 of 19] Compiling System.Posix.Files ( dist/build/System/Posix/Files.hs, dist/build/System/Posix/Files.o ) [ 9 of 19] Compiling System.Posix.IO ( dist/build/System/Posix/IO.hs, dist/build/System/Posix/IO.o ) [10 of 19] Compiling System.Posix.Temp ( dist/build/System/Posix/Temp.hs, dist/build/System/Posix/Temp.o ) [11 of 19] Compiling System.Posix.Process ( dist/build/System/Posix/Process.hs, dist/build/System/Posix/Process.o ) [12 of 19] Compiling System.Posix.Semaphore ( dist/build/System/Posix/Semaphore.hs, dist/build/System/Posix/Semaphore.o ) [13 of 19] Compiling System.Posix.SharedMem ( dist/build/System/Posix/SharedMem.hs, dist/build/System/Posix/SharedMem.o ) [14 of 19] Compiling System.Posix.Env ( dist/build/System/Posix/Env.hs, dist/build/System/Posix/Env.o ) [15 of 19] Compiling System.Posix.Directory ( dist/build/System/Posix/Directory.hs, dist/build/System/Posix/Directory.o ) [16 of 19] Compiling System.Posix.DynamicLinker.Prim ( dist/build/System/Posix/DynamicLinker/Prim.hs, dist/build/System/Posix/DynamicLinker/Prim.o ) [17 of 19] Compiling System.Posix.DynamicLinker ( dist/build/System/Posix/DynamicLinker.hs, dist/build/System/Posix/DynamicLinker.o ) [18 of 19] Compiling System.Posix.DynamicLinker.Module ( dist/build/System/Posix/DynamicLinker/Module.hs, dist/build/System/Posix/DynamicLinker/Module.o ) [19 of 19] Compiling System.Posix ( System/Posix.hs, dist/build/System/Posix.o ) /usr/bin/ar: creating dist/build/libHSunix-2.0.a ifBuildable/ifBuildable unix setup/Setup register --inplace Reading parameters from /var/lib/buildslave/ghc/mnemosyne-amd64-gentoo-head/build/libraries/unix/unix.buildinfo Registering unix-2.0... Reading package info from "dist/inplace-pkg-config" ... done. Saving old package config file... done. Writing new package config file... done. ifBuildable/ifBuildable base setup/Setup haddock Setup: Warning: Unknown field 'nhc98-options' Preprocessing library base-2.1... Running Haddock for base-2.1... haddock: modules are recursive: GHC.Storable GHC.Stable GHC.IOBase Foreign.C.Types Foreign.Storable Data.Typeable Data.HashTable GHC.ForeignPtr GHC.Exceptionmake[1]: *** [doc.library.base] Error 1 make[1]: Leaving directory `/var/lib/buildslave/ghc/mnemosyne-amd64-gentoo-head/build/libraries' make: *** [stage1] Error 2 -------------- next part -------------- Last 30 lines: [134 of 155] Compiling Data.ByteString.Lazy.Char8 ( Data/ByteString/Lazy/Char8.hs, dist/build/Data/ByteString/Lazy/Char8.p_o ) [135 of 155] Compiling GHC.TopHandler ( GHC/TopHandler.lhs, dist/build/GHC/TopHandler.p_o ) [136 of 155] Compiling System.Environment ( System/Environment.hs, dist/build/System/Environment.p_o ) [137 of 155] Compiling Control.Concurrent.MVar ( Control/Concurrent/MVar.hs, dist/build/Control/Concurrent/MVar.p_o ) [138 of 155] Compiling Control.Concurrent.QSem ( Control/Concurrent/QSem.hs, dist/build/Control/Concurrent/QSem.p_o ) [139 of 155] Compiling Control.Concurrent.QSemN ( Control/Concurrent/QSemN.hs, dist/build/Control/Concurrent/QSemN.p_o ) [140 of 155] Compiling Control.Concurrent.SampleVar ( Control/Concurrent/SampleVar.hs, dist/build/Control/Concurrent/SampleVar.p_o ) [141 of 155] Compiling Data.Array.Diff ( Data/Array/Diff.hs, dist/build/Data/Array/Diff.p_o ) [142 of 155] Compiling Data.Unique ( Data/Unique.hs, dist/build/Data/Unique.p_o ) [143 of 155] Compiling Control.Concurrent.Chan ( Control/Concurrent/Chan.hs, dist/build/Control/Concurrent/Chan.p_o ) [144 of 155] Compiling Control.Concurrent ( Control/Concurrent.hs, dist/build/Control/Concurrent.p_o ) [145 of 155] Compiling System.Timeout ( System/Timeout.hs, dist/build/System/Timeout.p_o ) [146 of 155] Compiling Control.Arrow ( Control/Arrow.hs, dist/build/Control/Arrow.p_o ) [147 of 155] Compiling Control.Applicative ( Control/Applicative.hs, dist/build/Control/Applicative.p_o ) [148 of 155] Compiling Data.Foldable ( Data/Foldable.hs, dist/build/Data/Foldable.p_o ) [149 of 155] Compiling Data.IntMap ( Data/IntMap.hs, dist/build/Data/IntMap.p_o ) [150 of 155] Compiling Data.Set ( Data/Set.hs, dist/build/Data/Set.p_o ) [151 of 155] Compiling Data.Traversable ( Data/Traversable.hs, dist/build/Data/Traversable.p_o ) [152 of 155] Compiling Data.Map ( Data/Map.hs, dist/build/Data/Map.p_o ) [153 of 155] Compiling Data.Sequence ( Data/Sequence.hs, dist/build/Data/Sequence.p_o ) [154 of 155] Compiling Data.Tree ( Data/Tree.hs, dist/build/Data/Tree.p_o ) [155 of 155] Compiling Data.Graph ( Data/Graph.hs, dist/build/Data/Graph.p_o ) <> Setup: dist/build/Control/Applicative_split: getDirectoryContents: does not exist (No such file or directory) make[2]: *** [build.library.base] Error 1 make[2]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build/libraries' make[1]: *** [stage1] Error 2 make[1]: Leaving directory `/64playpen/buildbot/x86_64-linux-head-unreg/build' From simonmarhaskell at gmail.com Wed Jun 6 05:44:15 2007 From: simonmarhaskell at gmail.com (Simon Marlow) Date: Wed Jun 6 05:39:42 2007 Subject: Suggestion re altering the build system In-Reply-To: <46660CF3.4030805@cse.unsw.edu.au> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> <4663C8A2.6080201@gmail.com> <46660CF3.4030805@cse.unsw.edu.au> Message-ID: <466681EF.9060508@gmail.com> Manuel M T Chakravarty wrote: > Simon Marlow wrote: >> Simon Peyton-Jones wrote: >>> | 1. We tag all the repos after a successful bootstrap on each >>> platform. >>> | Main problem with this: profusion of tags, obscuring 'darcs >>> changes' >>> | and 'darcs query tags'. Space itself isn't really an issue; a >>> tag >>> | only adds a few hundred bytes. >>> | >>> | We could mitigate the effect by rate-limiting the tags, say >>> only tag if >>> | there hasn't been a tag in the last week. Then we'd get one >>> | guaranteed-buildable state per week or so, which seems >>> reasonable. >>> | >>> | 2. We keep a separate set of repos that are only updated after a >>> successful >>> | build. Perhaps one set of repos per platform. >>> | Main problem with this: ensuring atomicity during the update >>> (probably >>> | not likely to be a significant problem in practice). >>> | Second problem: this doesn't store the repo state of every >>> successful >>> | build, only the most recent one. >>> | >>> | Personally I lean towards (2), as it's much easier to implement. >>> Any further >>> | comments? >>> >>> (2) seems good to me. Furthermore, if we published >>> Last good build is at repo >>> http://darcs.haskell.org/ghc-2007-02-09 >>> (so the date is in the repo name), and refrain from publishing until >>> the repo is really there, there'd be no atomicity issues would there? >>> >>> (We can just delete older ones after a bit.) >> >> Indeed, that's a good idea, although it's more work than just >> pushing. We wouldn't want to create a complete new set of repos for >> every successful build, I don't think. > > Similar rate limiting as you proposed for (1) could be applied; ie, no > more than one such repo per week. > > I don't quite understand why (2) is much easier to implement and having > a tag a week in the main tree marking a buildable state seems quite > attractive to me. Anyway, Option (2) is fine, too. For (2) I was thinking we could just add a target in the top-level Makefile that runs 'darcs push' for each of the repos, and invoke that as a step from buildbot. It's a bit simpler than having to invent a tag name, tag each repo and push the tags. If instead we had a new repo for each snapshot as per Simon PJ's suggestion, I would do it like this: after the initial darcs-all pull, tar up the whole tree. If the build succeeds, scp the tarball to darcs.haskell.org and unpack it in the right place. The snapshot repos would be partial, but that's hopefully not a problem. Again this can all be a target in the top-level Makefile invoked via BuildBot. (my builds have passwordless SSH access already because I upload the binary/source distributions to haskell.org). Andy's staging repo idea is interesting, but I think it's more work than the above two strategies, so we should see if the easy way is sufficient first. > However, just http://darcs.haskell.org/ghc-2007-02-09 isn't good enough. > We need a consistent set of ghc repo and core packages. Yes - I was assuming that we'd snapshot the core packages too (but not the extra packages). Cheers, Simon From simonpj at microsoft.com Wed Jun 6 06:00:34 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 05:56:00 2007 Subject: patch applied (testsuite): Add comments about runCmd Message-ID: <20070606100034.GA26260@cvs.haskell.org> Wed Jun 6 02:48:20 PDT 2007 simonpj@microsoft.com * Add comments about runCmd M ./driver/testlib.py +11 From Malcolm.Wallace at cs.york.ac.uk Wed Jun 6 06:49:26 2007 From: Malcolm.Wallace at cs.york.ac.uk (Malcolm Wallace) Date: Wed Jun 6 06:48:34 2007 Subject: patch applied (ghc): remove #if branches for pre-ghc-6.0 In-Reply-To: <20070606000816.GA13167@cvs.haskell.org> References: <20070606000816.GA13167@cvs.haskell.org> Message-ID: <20070606114926.53313f8f.Malcolm.Wallace@cs.york.ac.uk> Isaac Dupree wrote: > * remove #if branches for pre-ghc-6.0 > I skipped utils/hsc2hs/Main.hs since its ifs also involved > checking for old versions of nhc98 It's worth noting that hsc2hs was forked by ghc HQ, so the version in ghc/utils/hsc2hs is ghc-only, and no longer shared by either Hugs or nhc98 build trees, which use the separate main repo at http://darcs.haskell.org/hsc2hs I believe there is a desire to remove ghc's fork and re-integrate with the main repo at some point, but I couldn't find a ticket for it. Regards, Malcolm From simonpj at microsoft.com Wed Jun 6 09:10:59 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 09:06:23 2007 Subject: patch applied (testsuite): Add test for #1385 Message-ID: <20070606131059.GA31520@cvs.haskell.org> Wed Jun 6 06:10:53 PDT 2007 simonpj@microsoft.com * Add test for #1385 M ./tests/ghc-regress/typecheck/should_compile/all.T +1 A ./tests/ghc-regress/typecheck/should_compile/tc227.hs From simonpj at microsoft.com Wed Jun 6 09:12:39 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 09:08:01 2007 Subject: patch applied (ghc): Typo in comments Message-ID: <20070606131239.GA31673@cvs.haskell.org> Tue Jun 5 09:14:54 PDT 2007 simonpj@microsoft.com * Typo in comments M ./compiler/simplCore/SetLevels.lhs -1 +1 From simonpj at microsoft.com Wed Jun 6 09:12:43 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 09:08:05 2007 Subject: patch applied (ghc): FIX #1385: make sure tuple instances are loaded Message-ID: <20070606131243.GA31688@cvs.haskell.org> Wed Jun 6 06:00:56 PDT 2007 simonpj@microsoft.com * FIX #1385: make sure tuple instances are loaded Typechecking of explicit tuples is done "by hand" (rather than using boxySplitTyConApp) so that rigidity is maintained. In making that change I'd forgotten to retain the call to checkWiredInTyCon, which is important to make sure instances are brought into scope. Test is tc227. M ./compiler/typecheck/TcExpr.lhs -3 +5 From simonpj at microsoft.com Wed Jun 6 09:26:25 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 09:21:50 2007 Subject: patch applied (ghc): Remove unnecessary free-variables from renamer Message-ID: <20070606132625.GA32481@cvs.haskell.org> Wed Jun 6 06:25:21 PDT 2007 simonpj@microsoft.com * Remove unnecessary free-variables from renamer The renamer used to be responsible for making sure that all interfaces with instance decls (other than orphans) were loaded. But TH makes that impossible, so the typechecker does it, via checkWiredInTyCon. This patch simply removes redundant additions to the free-variable set in the renamer, which were there, I believe, solely to ensure that the instances came in. Removing them should change nothing, but it's a useful clean up. M ./compiler/iface/LoadIface.lhs +22 M ./compiler/iface/TcIface.lhs -1 +4 M ./compiler/rename/RnExpr.lhs -6 +3 M ./compiler/rename/RnTypes.lhs -10 +6 From simonpj at microsoft.com Wed Jun 6 09:41:43 2007 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Wed Jun 6 09:37:06 2007 Subject: patch applied (ghc): Don't suggest -fno-monomorphism-restriction if it's already set Message-ID: <20070606134143.GA731@cvs.haskell.org> Wed Jun 6 06:34:37 PDT 2007 simonpj@microsoft.com * Don't suggest -fno-monomorphism-restriction if it's already set This patch implements the suggestion in Trac #1398. It's obviously stupid to suggest -fno-monomorphism-restriction if the user is already using it. (Maybe another suggestion would be good, but this one clearly bogus.) M ./compiler/typecheck/TcSimplify.lhs -17 +24 From ghcbuild at microsoft.com Wed Jun 6 23:27:01 2007 From: ghcbuild at microsoft.com (GHC Build Reports) Date: Wed Jun 6 23:27:03 2007 Subject: [nightly] 06-Jun-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Message-ID: <20070607032701.A1F623241F6@www.haskell.org> Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location = /playpen/ghc/nightly/HEAD-cam-02-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Wed Jun 6 19:30:00 BST 2007. **** checking out new source tree ... ok. (GHC Version 6.7.20070606) **** Building stage 1 compiler ... ok. **** Building stage 2 compiler ... ok. **** Building stage 3 compiler ... ok. **** building testsuite tools ... ok. **** running tests ... ok (summary below). **** building compiler binary distribution ... ok. **** generating binary distribution + manifest ... ok. **** running nofib (-O) ... ok. (2 failures) **** running nofib (-O -fasm) ... ok. (2 failures) **** running nofib (-O -prof -auto-all) ... ok. (5 failures) **** running nofib (-O -prof -auto-all -fasm) ... ok. (5 failures) **** running nofib (-fasm) ... ok. (2 failures) **** running nofib (-unreg) ... failed. **** publishing distfiles ... Connection to haskell.org closed by remote host. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Received disconnect from 128.36.229.215: 2: Corrupted MAC on input. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Connection to haskell.org closed by remote host. lost connection failed. Read from remote host haskell.org: Connection reset by peer lost connection failed. **** publishing logs ... Connection to haskell.org closed by remote host. lost connection failed. **** publishing docs ... ok. Logs are at http://www.haskell.org/ghc/dist/current/logs Dists are at http://www.haskell.org/ghc/dist/current/dist Docs are at http://www.haskell.org/ghc/dist/current/docs All done! Nightly build finished successfully at Thu Jun 7 04:31:40 BST 2007 ------------- GHC Test summary --------------------- OVERALL SUMMARY for test run started at Wed Jun 6 22:34:10 BST 2007 1770 total tests, which gave rise to 9427 test cases, of which 18 caused framework failures 1692 were skipped 7417 expected passes 134 expected failures 2 unexpected passes 164 unexpected failures Unexpected passes: arith008(profasm) read032(normal) Unexpected failures: GMapAssoc(optc,hpc,profc,profasm) GMapTop(optc,hpc,profc,profasm) TH_exn2(normal) arith005(optc,hpc,optasm,profc,profasm,threaded2) arith008(hpc,threaded2) arith011(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) arith012(hpc,threaded2) barton-mangler-bug(profc) base01(normal) break014(ghci) break015(ghci) break016(ghci) break017(ghci) conc048(threaded2) conc052(profc,profasm) conc053(threaded1,threaded2) conc057(threaded2) conc063(normal,optc,hpc,optasm,profc,profasm,threaded1,threaded2) concprog001(ghci) drvfail001(normal) drvfail002(normal) drvfail003(normal) drvfail007(normal) dynbrk005(ghci) ffi-deriv1(normal,optc,hpc,optasm,profc,profasm) ffi009(threaded2) gadt23(normal) galois_raytrace(hpc,optasm,profasm,threaded2) getC(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ghc-e001(normal) ghci005(ghci) hGetBuf001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) haddock.Test(optc,profc) ind2(profc,profasm) lazypat(normal) maessen_hashtab(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) net001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) num012(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) par001(threaded1,threaded2) prog001(ghci) prog002(ghci) prog003(ghci) read008(normal) read040(normal,optc,hpc,optasm,profc,profasm) result001(ghci) rnfail028(normal) tcfail046(normal) tcfail072(normal) tcfail105(normal,optc,hpc,optasm,profc,profasm) tcfail118(normal) tcfail140(normal) tcfail145(normal) tcfail169(normal) tcfail177(normal) tcrun007(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) tcrun022(ghci) user001(normal,optc,hpc,optasm,profc,profasm,ghci,threaded1,threaded2) ---------------------------------------------------- Nightly run ended at Thu Jun 7 04:31:40 BST 2007 From chak at cse.unsw.edu.au Thu Jun 7 00:52:08 2007 From: chak at cse.unsw.edu.au (Manuel M T Chakravarty) Date: Thu Jun 7 00:47:33 2007 Subject: Suggestion re altering the build system In-Reply-To: <466681EF.9060508@gmail.com> References: <465ACB26.8060503@cse.unsw.edu.au> <465C2EC3.9090706@gmail.com> <465EADB0.4060901@cse.unsw.edu.au> <465EC971.5050204@gmail.com> <465F6547.5040705@cse.unsw.edu.au> <46603C2A.8090703@gmail.com> <4663C8A2.6080201@gmail.com> <46660CF3.4030805@cse.unsw.edu.au> <466681EF.9060508@gmail.com> Message-ID: <46678EF8.70605@cse.unsw.edu.au> Simon Marlow wrote, > Manuel M T Chakravarty wrote: >> I don't quite understand why (2) is much easier to implement and >> having a tag a week in the main tree marking a buildable state seems >> quite attractive to me. Anyway, Option (2) is fine, too. > > For (2) I was thinking we could just add a target in the top-level > Makefile that runs 'darcs push' for each of the repos, and invoke that > as a step from buildbot. It's a bit simpler than having to invent a tag > name, tag each repo and push the tags. > > If instead we had a new repo for each snapshot as per Simon PJ's > suggestion, I would do it like this: after the initial darcs-all pull, > tar up the whole tree. If the build succeeds, scp the tarball to > darcs.haskell.org and unpack it in the right place. The snapshot repos > would be partial, but that's hopefully not a problem. Again this can > all be a target in the top-level Makefile invoked via BuildBot. (my > builds have passwordless SSH access already because I upload the > binary/source distributions to haskell.org). > > Andy's staging repo idea is interesting, but I think it's more work than > the above two strategies, so we should see if the easy way is sufficient > first. > >> However, just http://darcs.haskell.org/ghc-2007-02-09 isn't good >> enough. We need a consistent set of ghc repo and core packages. > > Yes - I was assuming that we'd snapshot the core packages too (but not > the extra packages). Ok, sounds good. Manuel (who didn't get his ghc to re-build even after make distclean yesterday and now pulls todays patches wondering whether its going to be any better, or whether he has to pull - once again - a completely new tree of the repo *sigh*) From cvs-ghc at haskell.org Thu Jun 7 03:30:02 2007 From: cvs-ghc at haskell.org (BuildBot Collator) Date: Thu Jun 7 03:25:23 2007 Subject: Daily report for head Message-ID: <200706070730.l577U2vF026494@monk.galois.com> Build results: x86-64 Linux head: pass x86 Windows head: fail (failed bin dist) x86 Windows head fast: pass pass pass pass pass pass mnemosyne x86-64 Gentoo head: fail (failed stage1) x86-64 Linux head unreg: fail (failed stage1) New unexpected test failures: GMapAssoc 1 x86-64 Linux head GMapTop 1 x86-64 Linux head barton-mangler-bug 1 x86-64 Linux head base01 1 x86-64 Linux head conc052 1 x86-64 Linux head conc053 1 x86-64 Linux head conc057 1 x86-64 Linux head conc063 1 x86-64 Linux head concprog001 1 x86-64 Linux head gadt23 1 x86-64 Linux head hGetBuf001 1 x86-64 Linux head haddock.Test 1 x86-64 Linux head ind2 1 x86-64 Linux head maessen_hashtab 1 x86-64 Linux head net001 1 x86-64 Linux head par001 1 x86-64 Linux head print022 1 x86-64 Linux head read039 1 x86-64 Linux head tcrun022 1 x86-64 Linux head user001 1 x86-64 Linux head Fixed unexpected test failures: tc049 Old unexpected test failures: TH_exn2 2 x86-64 Linux head arith011 1 x86 Windows head fast break014 2 x86-64 Linux head break015 2 x86-64 Linux head break017 2 x86-64 Linux head drvfail001 2 x86-64 Linux head drvfail002 2 x86-64 Linux head drvfail003 2 x86-64 Linux head drvfail007 2 x86-64 Linux head dynbrk005 2 x86-64 Linux head ffi-deriv1 2 x86-64 Linux head getC 2 x86-64 Linux head ghc-e001 2 x86-64 Linux head ghciprog004 1 x86 Windows head fast lazypat 2 x86-64 Linux head list001 1 x86 Windows head fast prog003 2 x86-64 Linux head read008 2 x86-64 Linux head read040 2 x86-64 Linux head readwrite002 1 x86 Windows head fast result001 2 x86-64 Linux head rnfail028 2 x86-64 Linux head tcfail046 2 x86-64 Linux head tcfail072 2 x86-64 Linux head tcfail105 2 x86-64 Linux head tcfail118 2 x86-64 Linux head tcfail140 2 x86-64 Linux head tcfail145 2 x86-64 Linux head tcfail169 2 x86-64 Linux head tcfail177 2 x86-64 Linux head -------------- next part -------------- Last 30 lines: Finished making install-docs in unlit: 0 ------------------------------------------------------------------------ == make install-docs -wr; in /buildbot/x86-win-head/build/utils/touchy ------------------------------------------------------------------------ make[3]: Nothing to be done for `install-docs'. Finished making install-docs in touchy: 0 ------------------------------------------------------------------------ == Finished making `install-docs' in hp2ps unlit touchy ... PWD = /buildbot/x86-win-head/build/utils ------------------------------------------------------------------------ make[2]: Leaving directory `/buildbot/x86-win-head/build/utils' Renaming ghcprof to ghcprof.prl Renaming ghc-asm to ghc-asm.prl Renaming ghc-split to ghc-split.prl make -C libraries binary-dist make[2]: Entering directory `/buildbot/x86-win-head/build/libraries' ./../utils/mkdirhier/mkdirhier c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base mkdir c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries mkdir c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base ifBuildable/ifBuildable base cp base.cabal c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base ifBuildable/ifBuildable base cp -a dist c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base ifBuildable/ifBuildable base C:/cygwin/bin/find c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base/dist \ \( -name "*_split" -o -name "autogen" \) | xargs rm -rf rm: cannot remove directory `c:/builds/slave/x86-win-head/build/ghc-6.7.20070606/libraries/base/dist/build/Text/ParserCombinators/ReadPrec_split': Directory not empty make[2]: *** [binary-dist.library.base] Error 123 make[2]: Leaving directory `/buildbot/x86-win-head/build/libraries' make[1]: *** [binary-dist] Error 2 make[1]: Leaving directory `/buildbot/x86-win-head/build' -------------- next part -------------- Last 30 lines: unpackRLimit (18446744073709551615) = ... unpackRLimit (18446744073709551615) = ... [ 7 of 19] Compiling System.Posix.Error ( System/Posix/Error.hs, dist/build/System/Posix/Error.o ) [ 8 of 19] Compiling System.Posix.Files ( dist/build/System/Posix/Files.hs, dist/build/System/Posix/Files.o ) [ 9 of 19] Compiling System.Posix.IO ( dist/build/System/Posix/IO.hs, dist/build/System/Posix/IO.o ) [10 of 19] Compiling System.Posix.Temp ( dist/build/System/Posix/Temp.hs, dist/build/System/Posix/Temp.o ) [11 of 19] Compiling System.Posix.Process ( dist/build/System/Posix/Process.hs, dist/build/System/Posix/Process.o ) [12 of 19] Compiling System.Posix.Semaphore ( dist/build/System/Posix/Semaphore.hs, dist/build/System/Posix/Semaphore.o ) [13 of 19] Compiling System.Posix.SharedMem ( dist/build/System/Posix/SharedMem.hs, dist/build/System/Posix/SharedMem.o ) [14 of 19] Compiling System.Posix.Env ( dist/build/System/Posix/Env.hs, dist/build/System/Posix/Env.o ) [15 of 19] Compiling System.Posix.Directory ( dist/build/System/Posix/Directory.hs, dist/build/System/Posix/Directory.o ) [16 of 19] Compiling System.Posix.DynamicLinker.Prim ( dist/build/System/Posix/DynamicLinker/Prim.hs, dist/build/System/Posix/DynamicLinker/Prim.o ) [17 of 19] Compiling System.Posix.DynamicLinker ( dist/build/System/Posix/DynamicLinker.hs, dist/build/System/Posix/DynamicLinker.o ) [18 of 19] Compiling System.Posix.DynamicLinker.Module ( dist/build/System/Posix/DynamicLinker/Module.hs, dist/build/System/Posix/DynamicLinker/Module.o ) [19 of 19] Compiling System.Posix ( System/Posix.hs, dist/build/System/Posix.o ) /usr/bin/ar: creating dist/build/libHSunix-2.0.a ifBuildable/ifBuildable unix setup/Setup register --inplace Reading parameters from /var/lib/buildslave/ghc/mnemosyne-amd64-gentoo-head/build/libraries/unix/unix.buildinfo Registering unix-2.0... Reading package info from "dist/inplace-pkg-config" ... done. Saving old package config file... done. Writing new package config file... done. ifBuildable/ifBuildable base setup/Setup haddock Setup: Warning: Unknown field 'nhc98-options' Preprocessing library base-2.1... Running Haddock for base-2.1... haddock: modules are recursive: GHC.Storable GHC.Stable GHC.IOBase Foreign.C.Types Foreign.Storable Data.Typeable Data.HashTable GHC.ForeignPtr GHC.Exc