Buildbot: "Latest Successful Build" for each builder?

[Simon Marlow]

Ian Lynagh wrote:
> Hi Claus,
> 
> On Sat, Aug 02, 2008 at 07:10:31PM +0100, Claus Reinke wrote:
>>>> But there seems to be no "Latest Successful Build" for each builder,
>>> but of course we have other priorities in the build-up to release.
>> That confuses me everytime: how can you build up for a release
>> without working builds?-)
> 
> I wasn't talking about working builds, I was talking about a
> "Latest Successful Build" column for each builder. If you understand the
> build failure then knowing when the last successful build was doesn't
> generally help you.
> 
>> 'make; make binary-dist' was recommended to me many years
>> ago by the folks responsible for making windows snapshots as
>> the standard way of getting a tar-able relocatable directory full
>> of GHC goodness on windows, right at the top of the ghc tree
>> (iirc, one originally had to call some prep-bin-dist-mingw as well). 
>>
>> I've been happy with that procedure since then, provided the
>> make target isn't broken. Are you saying that has changed as 
>> well, and I should use 'make install' instead in future? Is that
>> less broken right now?
> 
> Both should work in general, but last time I checked "install" worked
> and "binary-dist" didn't.
> 
> However, I think the Windows build is currently broken again anyway.
> I've just pushed a few fixes, but with -Werror it fails for me with:
> 
>     Linker.c: In function `ocResolve_PEi386':
>     Linker.c:2512:0:
>          warning: implicit declaration of function `lookupLocalSymbol'
> 
> while without -Werror it gets further, but eventually falls over with:
> 
>     Linking dist-stage2\build\ghc\ghc.exe ...
>     C:/msys/1.0/home/ian/ghc/rts/libHSrts_thr.a(Linker.thr_o)(.text+0xf9a):Linker.c:
>     undefined reference to `lookupLocalSymbol'
>     C:/msys/1.0/home/ian/ghc/rts/libHSrts_thr.a(Linker.thr_o)(.text+0xfc9):Linker.c:
>     undefined reference to `lookupLocalSymbol'
>     collect2: ld returned 1 exit status
> 
> It looks like this was caused by:
> 
>     [FIX #2375: remove oc->lochash completely, it apparently isn't used
>     Simon Marlow <marlowsd at gmail.com>**20080730101252] {
> 
> Do you know what's going on, Simon?

Sorry, my bad.  I've rolled back the patch and I'm validating a fix.

Cheers,
	Simon