On Mon, Sep 29, 2008 at 10:46:34AM +0100, Ian Lynagh wrote:
> > BTW: I had some problems running the testsuite some weeks ago,
> > because some autoconf'd stuff was missing. When building from the
> > repository (*not* from the source tarballs), are there any additional
> > steps beyond
> >
> > sh boot
> > ./configure --prefix=...
> > gmake install
> >
> > required?
>
> I'm not sure if running "gmake install" without first running "gmake"
> works. Also, note that if you are building the extralibs then you need
> to run "sh boot" after getting them.
I was sloppy in my mail. Actually I'm even building stage1 and stage2
explicitely before installing. From my script:
nice time gmake stage1
nice time gmake stage2
nice time gmake install
And my problem with the testsuite was a PEBKAC (of course): on
OpenBSD, python is installed as python-2.3, python-2.4, python-2.5
(you can have several versions installed in parallel), which isn't
found by configure, which in turn lets the testsuite bail out.
Setting PythonCmd during configure fixed it.
I've yet to evaluate the results of the testsuite. I'll post it in
a few hours.
Ciao,
Kili
_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
