List Info

Thread: Errors building hat 2.04




Errors building hat 2.04
user name
2006-10-01 19:52:28
hi all, after running configure on the latest release of
hat, 'make' gives me:

>>>
/export/home/yang/tmp/pkg/hat-2.04/lib/ix86-Linux/config:11:
***
missing separator.  Stop.
>>>

that config file contains:

>>>
BUILDWITH=ghc
BUILDOPTS=""
INSTALLVER="2.04"
INSTALLINFO="config: ix86-Linux/ by yangharvard.csail.mit.edu on  1 Oct 2006"
BUILDBASEDIR=/home/yang/tmp/pkg/hat-2.04/targets
LIBCOMPAT=""
EXE=
CC=gcc
GHCSYM=

604
TRUE=/bin/true
GLIB=glib
>>>

i thought maybe the whitespace before 604 needed to be
removed. doing
that, 'make' continues fine, until...

>>>
...
ghc -package-name hat -fglasgow-exts -package base -package
parsec -package mtl
-fno-warn-overlapping-patterns -fno-warn-missing-methods
-fno-warn-duplicate-exports
-i/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/
ghc -I.
-I/export/home/yang/tmp/pkg/hat-2.04/include  '-#include
"hat-c.h"'
-cpp -c -o
/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/gh
c/Hat/Hack.o
Hat/Hack.hs
mv  Hat/Hack.hi
/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/gh
c/Hat/Hack.hi
ghc -package-name hat -fglasgow-exts -package base -package
parsec -package mtl
-fno-warn-overlapping-patterns -fno-warn-missing-methods
-fno-warn-duplicate-exports
-i/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/
ghc -I.
-I/export/home/yang/tmp/pkg/hat-2.04/include  '-#include
"hat-c.h"'
-cpp -c -o
/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/gh
c/Hat/PreludeBuiltinTypes.o
Hat/PreludeBuiltinTypes.hs
mv  Hat/PreludeBuiltinTypes.hi
/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/gh
c/Hat/PreludeBuiltinTypes.hi
/export/home/yang/tmp/pkg/hat-2.04/script/hat-trans -P. -I.
-trusted
-prelude -D__GLASGOW_HASKELL__=  604 PreludeBuiltin.hs
Can't open 604
make[1]: ***
[/home/yang/tmp/pkg/hat-2.04/targets/ix86-Linux/obj/hatlib/g
hc/Hat/PreludeBuiltin.o]
Error 1
make[1]: Leaving directory
`/export/home/yang/tmp/pkg/hat-2.04/src/hatlib'
make: *** [targets/ix86-Linux/hat-lib-ghc] Error 2
>>>

how do i fix this build problem? i read this thread:

http://www.haskell.org/pipermail/hat/2006-February
/000256.html

but that patch was already applied in the release i
downloaded.

thanks in advance for any help.
_______________________________________________
Hat mailing list
Hathaskell.org
http://ww
w.haskell.org/mailman/listinfo/hat
Errors building hat 2.04
user name
2006-10-02 11:12:33
"Yang" <d9jh00502sneakemail.com> wrote:

> hi all, after running configure on the latest release
of hat, 'make'
> gives me:
> 
> >>> missing separator.  Stop.

Yes, this seems to be the same error as in the mail thread
you quoted.

> GHCSYM=
> 
> 604
> 
> i thought maybe the whitespace before 604 needed to be
removed. doing
> that, 'make' continues fine, until...
>
> hat-trans ... -D__GLASGOW_HASKELL__=  604

Ensure that there is no whitespace at all, i.e.
  GHCSYM=604

If the patch to the 'configure' script did not work, then
you may also
need to make a similar change in the file
targets/`harch`/ghcsym

Regards,
    Malcolm
_______________________________________________
Hat mailing list
Hathaskell.org
http://ww
w.haskell.org/mailman/listinfo/hat
Errors building hat 2.04
user name
2006-10-02 11:52:29
Malcolm,
   This seems to be a recurring problem.  Do we have a list
of what  
ghc produces on each platform?  If we had that, I guess we
could find  
a regexp that works on all known systems.

Bob

On 2 Oct 2006, at 12:12, Malcolm Wallace wrote:

> "Yang" <d9jh00502sneakemail.com> wrote:
>
>> hi all, after running configure on the latest
release of hat, 'make'
>> gives me:
>>
>>>>> missing separator.  Stop.
>
> Yes, this seems to be the same error as in the mail
thread you quoted.
>
>> GHCSYM=
>>
>> 604
>>
>> i thought maybe the whitespace before 604 needed to
be removed. doing
>> that, 'make' continues fine, until...
>>
>> hat-trans ... -D__GLASGOW_HASKELL__=  604
>
> Ensure that there is no whitespace at all, i.e.
>   GHCSYM=604
>
> If the patch to the 'configure' script did not work,
then you may also
> need to make a similar change in the file
targets/`harch`/ghcsym
>
> Regards,
>     Malcolm
> _______________________________________________
> Hat mailing list
> Hathaskell.org
> http://ww
w.haskell.org/mailman/listinfo/hat

_______________________________________________
Hat mailing list
Hathaskell.org
http://ww
w.haskell.org/mailman/listinfo/hat
Errors building hat 2.04
user name
2006-10-02 13:47:17
Thomas Davie <tatd2kent.ac.uk> wrote:

>    This seems to be a recurring problem.  Do we have a
list of what  
> ghc produces on each platform?  If we had that, I guess
we could find 
> a regexp that works on all known systems.

It's not so much ghc, as _gcc_, because the extra
whitespace/#pragmas
are inserted by the C preprocessor.  I believe the regexp
currently in
CVS is correct (not "^#" and not "^$"),
but perhaps an alternative which
actually searches for numbers on a line of their own (e.g.
"^[0-9]*$")
might be better.

Regards,
    Malcolm
_______________________________________________
Hat mailing list
Hathaskell.org
http://ww
w.haskell.org/mailman/listinfo/hat
Errors building hat 2.04
user name
2006-10-04 01:26:17
to be honest, as much as i'd love contributing, i often
don't have the
time to go in and debug software that i'm trying/evaluating.
(as i
said, the patch was already applied in the tarball i
downloaded.) such
pursuits almost always turn into much deeper time sinks than
how
they're initially presented to me.

when will the next version be available that fixes this?
i'll wait for
that. thanks.

On 10/2/06, Malcolm Wallace Malcolm.Wallace-at-cs.york.ac.uk
|hat|
<...> wrote:
> Thomas Davie <tatd2kent.ac.uk> wrote:
>
> >    This seems to be a recurring problem.  Do we
have a list of what
> > ghc produces on each platform?  If we had that, I
guess we could find
> > a regexp that works on all known systems.
>
> It's not so much ghc, as _gcc_, because the extra
whitespace/#pragmas
> are inserted by the C preprocessor.  I believe the
regexp currently in
> CVS is correct (not "^#" and not
"^$"), but perhaps an alternative which
> actually searches for numbers on a line of their own
(e.g. "^[0-9]*$")
> might be better.
>
> Regards,
>     Malcolm
> _______________________________________________
> Hat mailing list
> Hathaskell.org
> http://ww
w.haskell.org/mailman/listinfo/hat
>
_______________________________________________
Hat mailing list
Hathaskell.org
http://ww
w.haskell.org/mailman/listinfo/hat
[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )