headers
tim.beech | 9 Dec 2012 15:53
Picon
Gravatar

building GHC for Slackware/Salix

I'm making a GHC package for Salix 14 (which is backwards-compatible with
Slackware, so this will be a Slackware package, too).

The main thing I'd be grateful for advice on is the overall approach I'm
taking to the package. Others I've seen (such as the Arch package) just
assume GHC is already present.

My build script unpacks the binary distribution for "unknown linux" and
builds GHC against that. (Both are version 7.4.2.) I have avoided
installing anything else (such as the Haskell Platform) so as to keep as
close as possible to the ideal of a package as a transparent,
reproducible process that only depends on the source. As far as I can
tell from the build prerequisites

http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation/Tools

the only consequence is that documentation is only created as html, not
pdf and ps as well.

Though everything seems to work ok, the build as it stands fails three tests:

Unexpected failures:
lib/Time T5430 [bad stdout] (normal)
perf/compiler parsing001 [stat not good enough] (normal)
simplCore/should_compile spec-inline [stderr mismatch] (optasm)

That is after running the fast version of the test suite, which the
documentation says should pass 100%.

My second question is, do these results suggest anything as to where the
(Continue reading)

Permalink | Reply |
headers
Tim Beech | 14 Dec 2012 15:35
Picon
Gravatar

Re: building GHC for Slackware/Salix

I've now tried a build strictly according to the instructions, which
is to say, I installed the binary distribution, then haskell-platform
on top of it, before building GHC from source. I get the same errors,
plus a few more (I did the quick build rather than the fully optimized
default build, so maybe that's why; most of the extra failures are
from perf/compiler and say "stat not good enough").
Out of curiosity, I unpacked the bindist tarball afresh and ran the
failed tests on it. They also failed (the third one in a few more
ways):

Unexpected failures:
   lib/Time  T5430 [bad stdout]
(normal,hpc,optasm,profasm,threaded1,threaded2,dyn,profthreaded)
   lib/Time  T5430 [bad stdout or stderr] (ghci)

All this makes me think there is something wrong with my setup. I'd be
very grateful if anyone has any suggestions - or if this is the wrong
place for these questions, where would be a better place.

Tim

On 09/12/2012, tim.beech <tim.beech <at> gmail.com> wrote:
> I'm making a GHC package for Salix 14 (which is backwards-compatible with
> Slackware, so this will be a Slackware package, too).
>
> The main thing I'd be grateful for advice on is the overall approach I'm
> taking to the package. Others I've seen (such as the Arch package) just
> assume GHC is already present.
>
> My build script unpacks the binary distribution for "unknown linux" and
(Continue reading)

Permalink | Reply |
headers
Ian Lynagh | 16 Dec 2012 16:18
Favicon

Re: building GHC for Slackware/Salix


Hi Tim,

On Sun, Dec 09, 2012 at 11:53:32AM -0300, tim.beech wrote:
> 
> My build script unpacks the binary distribution for "unknown linux" and
> builds GHC against that. (Both are version 7.4.2.) I have avoided
> installing anything else (such as the Haskell Platform) so as to keep as
> close as possible to the ideal of a package as a transparent,
> reproducible process that only depends on the source. As far as I can
> tell from the build prerequisites
> 
> http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation/Tools
> 
> the only consequence is that documentation is only created as html, not
> pdf and ps as well.

You don't need the haskell-platform to build the docs; I suspect you're
missing dblatex.

> Unexpected failures:
> lib/Time T5430 [bad stdout] (normal)
> perf/compiler parsing001 [stat not good enough] (normal)
> simplCore/should_compile spec-inline [stderr mismatch] (optasm)
> 
> That is after running the fast version of the test suite, which the
> documentation says should pass 100%.
> 
> My second question is, do these results suggest anything as to where the
> problem may lie, and how important it is?
(Continue reading)

Permalink | Reply |
headers
tim.beech | 16 Dec 2012 19:37
Picon
Gravatar

Re: building GHC for Slackware/Salix

Dear Ian,

Thanks for your response. Here is the output of the bad tests:

http://pastebin.com/iepNQPf0

Since first posting to the haskell-users list, I have tried several
other builds with similar results. This one simply unpacks the
unknown-linux bindist of GHC (as well as building the versions of gmp
and libffi it needs) and builds from the GHC source against that. Here
is what's passed to configure:

./configure --prefix=/usr --libdir=/usr/lib${LIBDIRSUFFIX}
--mandir=/usr/man --docdir=/usr/doc/$pkgname-$pkgver
--with-ghc=$startdir/src/stage_0_build/usr/bin/ghc

For what it's worth, here is the whole thing - but I doubt it's
relevant:

http://people.salixos.org/mimosa/packages/ghc/7.4.2/SLKBUILD.new

Unless there is an absolute necessity, I'd prefer to build it without
any other Haskell bits and pieces. But if this isn't possible, what *is*
needed? I have already established that the Haskell Platform alone isn't
sufficient to make these errors go away.

The problem with the build script for Haskell Platform turns out to be
an error in the script, nothing to do with needing to be root to execute
the recache command. You are also right that Haskell Platform makes no
difference to the way the documentation is built. I saw dblatex on the
(Continue reading)

Permalink | Reply |
headers
tim.beech | 17 Dec 2012 14:18
Picon
Gravatar

Re: building GHC for Slackware/Salix

Dear Ian,

I'm not sure if I mentioned that the binary distribution fails those
tests too, and several others on top:

http://pastebin.com/E45cTqvy

To get from thirteen failures to three is at least an improvement!

Tim
Permalink | Reply |

Gmane