ghc-testsuite-6.6 on Macs

Thorkil Naur naur at
Mon Nov 13 18:50:53 EST 2006


This is an attempt to address (a very small part of) this: On my PowerPC Mac 
OS X 10.3 (Panther, I think, not Tiger as I have written elsewhere), I have 
built the ghc-6.6 branch (of about 2006-Nov-07 19.00 UTC) using (The Glorious Glasgow Haskell Compilation System, version 
6.4.1) that I got from I 
haven't studied the details of Cabal yet, so to work around an X11 problem 
(, I did 
(1) darcs get of the ghc-6.6 branch; (2) sh darcs-all get (without --extra); 
(3) got through gmake of everything without failing; (4) sh darcs-all --extra 
get (to get the extra libraries, some of which (e.g. QuickCheck) are needed 
for some of the tests); and finally (5) repeated gmake of everything, failing 
at the X11 build, but getting through the QuickCheck build.

Then I "darcs got" the ghc-6.6/testsuite and ran the tests. My hope was that I 
would be able to reproduce something similar to, 
although under different circumstances.

So far, I have only analysed the barton-mangler-bug test in detail. I have 
produced an experimental darcs patch that solves some problems, while 
possibly introducing others: . 
Comments to this would be most welcome.

Best regards

On Tuesday 07 November 2006 12:39, Christian Maeder wrote:
> Simon Marlow schrieb:
> >>    ghcpkg01(normal)
> >>    ghcpkg03(normal)
> > 
> > Any idea why these are failing for you?
> Maybe rather than using my installed ghc-pkg (that lists haskell-src)
> some inplace ghc-pkg was used:
> ghc-pkg: dependency haskell-src doesn't exist (use --force to override)
> make[2]: *** [ghcpkg01] Fehler 1
> >> I thought the failure signals002(ghci) was related to
> >>
> >> In fact, I needed to kill the ghc-process to continue the tests.
> >>
> >> The test files cc004.hs and ffi012.hs failed with several messages of
> >> the form:
> >>
> >>     calling convention not supported on this architecture: stdcall
> >>     When checking declaration:
> >>         foreign import stdcall safe "wrapper"
> >>             wrap_f :: F -> IO (FunPtr F)
> >>
> >> However, they did not make it into the summary
> > 
> > They are probably expected failures for you.
> Yes they are indeed, but should these really be "expected failures"?
> > some of those could be floating-point differences.  In any case, it
> > would be good to investigate all of them and get any expected failures
> > registered properly in the testsuite.  Can you (or someone else) take a
> > look and find out why each of them is failing?
> Yes, I hope someone else joins in.
> Christian
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at

More information about the Glasgow-haskell-users mailing list