Hi!
I start to hack GHC, and, I 've tried to build it, but the build return
this error message :
./compiler/stage1/ghc-inplace -o stage2/ghc -H64m -Onot -fasm -package ghc
-Ist age2 -cpp -fglasgow-exts -fno-generics -Rghc-timing
-I. -IcodeGen -InativeGen -I
Hello,
Rodrigo Geraldo wrote:
I start to hack GHC, and, I 've tried to build it, but the build
return
this error message :
configure: GMP_CHECK_ASM_W32: fatal: do not know how to define a 32-
bit word
make[1]: *** [boot] Error 1
I've tried to build GHC using mSYS and MinGW under MS
Hi!
I start to hack GHC, and, I 've tried to build it, but the build return
this error message :
configure: GMP_CHECK_ASM_W32: fatal: do not know how to define a 32-bit word
make[1]: *** [boot] Error 1
I've tried to build GHC using mSYS and MinGW under MS windows xp...
Does anyone have any
Simon Marlow wrote:
Michael Marte wrote:
Now I get the following error:
GHC/PrimopWrappers.hs:565:20: Not in scope: `GHC.Prim.forkOn#'
I think this problem may be releated to the other changes I pulled.
You probably need to rebuild some stuff. If your stage 1 compiler is
up to date,
Simon Marlow wrote:
Michael Marte wrote:
Yes, I synced my working copy of ghc 6.5 yesterday with darcs pull.
Are there any requirements as to which exact version of ghc 6.4 I am
supposed to use?
I am using the plain 6.4 release but I am able to build the head of
the 6.4 branch.
BTW. Am I
Michael Marte wrote:
I did as you said (make clean; autoreconf; configure; make) but it
didn't help; I get the same error as before.
Ok, could you try this:
$ size ghc/lib/compat/cbits/unicode.o
$ size ghc/lib/compat/Compat/Unicode.o
there should be some code in those modules if the
Simon Marlow wrote:
Michael Marte wrote:
I did as you said (make clean; autoreconf; configure; make) but it
didn't help; I get the same error as before.
Ok, could you try this:
$ size ghc/lib/compat/cbits/unicode.o
$ size ghc/lib/compat/Compat/Unicode.o
there should be some code in
Michael Marte wrote:
Simon Marlow wrote:
Michael Marte wrote:
I did as you said (make clean; autoreconf; configure; make) but it
didn't help; I get the same error as before.
Ok, could you try this:
$ size ghc/lib/compat/cbits/unicode.o
$ size ghc/lib/compat/Compat/Unicode.o
there
Simon Marlow wrote:
Michael Marte wrote:
Simon Marlow wrote:
Michael Marte wrote:
I did as you said (make clean; autoreconf; configure; make) but it
didn't help; I get the same error as before.
Ok, could you try this:
$ size ghc/lib/compat/cbits/unicode.o
$ size
Michael Marte wrote:
Now I get the following error:
GHC/PrimopWrappers.hs:565:20: Not in scope: `GHC.Prim.forkOn#'
I think this problem may be releated to the other changes I pulled.
You probably need to rebuild some stuff. If your stage 1 compiler is up
to date, then remove
Michael Marte wrote:
Hello *,
when building ghc 6.5 with ghc 6.4 and alex 2.0.1, the build fails as
follows:
make -C ghc/compiler stage=2
make[2]: Entering directory `/home/marte/fptools/ghc/compiler'
../../ghc/compiler/ghc-inplace -H16m -O -istage2/utils
-istage2/basicTypes
Simon Marlow wrote:
Michael Marte wrote:
Hello *,
when building ghc 6.5 with ghc 6.4 and alex 2.0.1, the build fails as
follows:
make -C ghc/compiler stage=2
make[2]: Entering directory `/home/marte/fptools/ghc/compiler'
../../ghc/compiler/ghc-inplace -H16m -O -istage2/utils
Michael Marte wrote:
Yes, I synced my working copy of ghc 6.5 yesterday with darcs pull.
Are there any requirements as to which exact version of ghc 6.4 I am
supposed to use?
I am using the plain 6.4 release but I am able to build the head of the
6.4 branch.
BTW. Am I supposed to run
Hello *,
when building ghc 6.5 with ghc 6.4 and alex 2.0.1, the build fails as
follows:
make -C ghc/compiler stage=2
make[2]: Entering directory `/home/marte/fptools/ghc/compiler'
../../ghc/compiler/ghc-inplace -H16m -O -istage2/utils
-istage2/basicTypes -istage2/types -istage2/hsSyn
On Sun, Jun 08, 2003 at 01:40:42PM +0100, Ian Lynagh wrote:
I'm having problems building GHC 6.0 with GCC 3.3. I've fixed a couple
If it helps, I've just done a stage 1 build with SplitObjs = NO in
mk/build.mk and it makes hello world fine.
Also, I forgot to include this last time:
$ gcc -v
I'm having problems building GHC 6.0 with GCC 3.3. I've fixed a couple
of problems with comments in CPP macros as seen elsewhere, and then
everything seemed to be going fine until it came to create
stage2/ghc-6.0 and it failed with a huge number of things like
stage2/utils/Util.o(.text+0xb8
Hi,
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS repository carries. (Is
that supposed to
In local.glasgow-haskell-users, you wrote:
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS
Volker Stolz writes:
Where did you find those instructions?
At http://haskell.cs.yale.edu/ghc/docs/latest/html/building/sec-cvs.html:
| 2.4. Updating Your Source Tree
|
| It can be tempting to cvs update just part of a source tree to bring in
| some changes that someone else has made, or
Alastair: Thanks a lot for the detailed reply! I'll take a look at the
build again; maybe I can get this problem fixed after all.
The attached diff (about to be committed) seems to fix the problem.
--
Alastair? gc-3.00
? distrib/html/old_index.html
? lib/Foreign/GreenCard.p_hi
?
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS repository carries.
Sorry about that, the
Alastair Reid writes:
The attached diff (about to be committed) seems to fix the problem.
It does indeed -- thank you very much for your help!
One problem remains, though: When I build GHC from the top-level
directory, the build process does get the order right. It tries to
build
Simon Marlow writes:
CVS doesn't really support the structure of our source tree very
well.
Actually, it does. ;-)
The problem is that »ghc«, »green-card«, »hood« et al. are
subdirectories of »fptools«, that's why »cvs update -d« retrieves them
automatically. I guess a more appropriate
In local.glasgow-haskell-users, you wrote:
| 2.4. Updating Your Source Tree
| It can be tempting to cvs update just part of a source tree to bring in
| some changes that someone else has made, or before committing your own
| changes. This is NOT RECOMMENDED! [...]
|
| So, to avoid a lot of
Volker Stolz writes:
[STABLE branch]
Does the »STABLE« branch contain the meta-haskell extensions already?
Because this was the reason I wanted to run the CVS version in the
first place. :-)
Oh, and I have news: The build does not work yet, unfortunately. It
fails here:
|
The problem is that ghc, green-card, hood et al. are
subdirectories of fptools, that's why cvs update -d retrieves them
automatically. I guess a more appropriate repository layout would be
_flat_, like this:
/cvs --+
|
+-- CVSROOT
|
+--
Simon Marlow writes:
We could just rearrange the repository in place, and everything would
still work, right?
It's not quite that easy, unfortunately. If you want to retain the
files's version history (and I guess you would), then you have to move
the directories around in the CVS
Simon Marlow [EMAIL PROTECTED] writes:
/cvs --+
|
+-- CVSROOT
|
+-- fptools
|
+-- ghc
|
+-- libraries
|
+-- hslibs
|
Simon Marlow writes:
We could just rearrange the repository in place, and
everything would
still work, right?
It's not quite that easy, unfortunately. If you want to retain the
files's version history (and I guess you would), then you have to move
the directories around in the
Title: Problems building GHC 5.00 on Solaris 2.5.1
I'm trying to build GHC 5.00 on Solaris 2.5.1.
I've got most of the way there. So far, I've had to:
- Hack glafp-utils/sgmlverb/Makefile because by lex doesn't support the -8 option.
- Hack mk/target.mk in several places because my ld
30 matches
Mail list logo
