#5489: Win7: Bootstrapping 7.3 from 7.2.1 using msys git 1.7.6 causes
integer-gmp
./configure to fail
--+-
Reporter: btutt| Owner: igloo
Type: bug | Status
#5489: Win7: Bootstrapping 7.3 from 7.2.1 using msys git 1.7.6 causes
integer-gmp
./configure to fail
--+-
Reporter: btutt | Owner: igloo
Type: bug| Status: patch
#5489: Win7: Bootstrapping 7.3 from 7.2.1 using msys git 1.7.6 causes
integer-gmp
./configure to fail
--+-
Reporter: btutt |Owner:
Type: bug| Status
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
---+
Reporter: igloo | Owner:
Type: task | Status: closed
Priority: high
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
-+--
Reporter: igloo |Owner:
Type: task | Status: new
Priority: high
#4012: Different stage2 results depending on the version of the bootstrapping
compiler
---+
Reporter: kili | Owner:
Type: bug | Status: closed
.
The bootstrapping GHC is a red herring, as I mentioned - the fact is that
compilation results aren't deterministic. They never have been, in fact.
Even if compilation results were deterministic, under what circumstances
would you want to have two systems use each others packages, when
they're both using
#4012: Different stage2 results depending on the version of the bootstrapping
compiler
-+--
Reporter: kili | Owner:
Type: bug | Status: new
#4012: Different stage2 results depending on the version of the bootstrapping
compiler
-+--
Reporter: kili | Owner:
Type: bug | Status: new
#4012: Different stage2 results depending on the version of the bootstrapping
compiler
---+
Reporter: kili | Owner:
Type: bug | Status: closed
#4012: Different stage2 results depending on the version of the bootstrapping
compiler
---+
Reporter: kili | Owner:
Type: bug | Status: closed
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
---+
Reporter: igloo | Owner:
Type: task | Status: new
Priority: high
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
---+
Reporter: igloo | Owner:
Type: task | Status: new
Priority: high
#3623: Host's C info ending up in .hc files while cross-bootstrapping
--+-
Reporter: ksf | Owner:
Type: bug | Status: closed
Priority: normal
#3623: Host's C info ending up in .hc files while cross-bootstrapping
-+--
Reporter: ksf | Owner:
Type: bug | Status: new
Priority: normal
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
-+--
Reporter: igloo |Owner:
Type: task | Status: new
Priority: normal
#3556: Build the bootstrapping ghc-pkg with ghc-cabal
---+
Reporter: igloo | Owner:
Type: task | Status: new
Priority: normal
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
--+-
Reporter: cspiel| Owner:
Type: bug | Status: closed
Priority: normal| Milestone
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
---+
Reporter: cspiel | Owner:
Type: bug | Status: new
Priority: normal | Component: Build System
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
-+--
Reporter: cspiel|Owner:
Type: bug | Status: new
Priority: normal|Milestone
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
-+--
Reporter: cspiel|Owner:
Type: bug | Status: new
Priority: normal|Milestone
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
-+--
Reporter: cspiel|Owner:
Type: bug | Status: new
Priority: normal|Milestone
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
--+-
Reporter: cspiel| Owner:
Type: bug | Status: new
Priority: normal| Milestone
#2794: Bootstrapping ghc-6.4.3 hangs in call to ghc-pkg-inplace
--+-
Reporter: cspiel| Owner:
Type: bug | Status: new
Priority: normal| Milestone
On Fri, 2007-08-17 at 11:33 +0100, Malcolm Wallace wrote:
Duncan Coutts [EMAIL PROTECTED] wrote:
Is it still possible to upgrade an older version of Cabal (e.g.
supplied with ghc-6.2) to the latest version, using only the older
version of Cabal itself?
We've never supported
Priority: 5
Submitted By: Andy Dougherty (doughera)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bootstrapping fails at System/CPUTime_hsc.c
Initial Comment:
I have been attempting to bootstrap ghc-6.4 on a
Solaris 2.8/SPARC system
with no previous version of ghc installed. I'm
currently stuck
: None
Priority: 5
Submitted By: Andy Dougherty (doughera)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bootstrapping fails at System/CPUTime_hsc.c
Initial Comment:
I have been attempting to bootstrap ghc-6.4 on a
Solaris 2.8/SPARC system
with no previous version of ghc installed. I'm
currently
eek! You really should have checked with us before trying to build the CVS
HEAD
That _was_ me checking with you :-)
(The timezone difference imposes a 24 hour delay on communication so I try to
put a decent amount of information into messages, try things out myself, etc.)
so, "cvs co -r
~
Tried bootstrapping with ghc-4.07(ish).
# Used something like this sequence on this attempt
cvs checkout fpconfig
cd fptools
cvs checkout happy ghc hslibs
autoconf
(cd ghc autoconf)
GHC=ghc-4.07 ./configure --prefix=$HOME/local
make boot
Failed in make boot because ghc-4.07 doesn't
Building 4.07 with 4.06 works fine, but in a second bootstrapping
phase the fresh 4.07 can't compile itself, at least not with
"SRC_HC_OPTS += -O". Without -O everything seems to work...
We know about this one. I'm about to commit a hack, and Simon will follow
up with the Real
Building 4.07 with 4.06 works fine, but in a second bootstrapping
phase the fresh 4.07 can't compile itself, at least not with
"SRC_HC_OPTS += -O". Without -O everything seems to work...
Cheers,
Sven
...
g
Jan Kort [EMAIL PROTECTED] writes:
It looks like I'm either missing more code, or I'm on the wrong
track. I can't find the powerpc assembly code for "JMP_" (should
be in ghc/includes/TailCalls.h), "StgRun" (should be in
ghc/rts/StgCRun.c) and for "StgReturn" (should be in ghc/rts/StgRun.S).
Sigbjorn Finne (Intl Vendor) wrote:
Jan Kort [EMAIL PROTECTED] writes:
Thanks, I can get a lot further now, everything apart from
compiling the assembler files and linking the hsc works, but
that will have to wait till tommorow :)
Jan
Great, if you should get stuck while
Jan Kort [EMAIL PROTECTED] writes:
Hi,
I tried to bootstrap ghc4.00 on AIX with the "--enable-hc-boot"
flag, but I got an error:
[]
make[2]: *** [all] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1
Which I don't understand, am I missing some hc files ?
Hi,
In ghc/Makefile it says:
17 # Order is important! driver/ has to come before includes/ which
18 # again has to come before the rest.
19 #
20 # If we're booting from .hc files, swap the order
21 # we descend into compiler/ and lib/
22 #
23 ifeq
looks like the variable HAPPY in ghc/compiler/Makefile is not
defined, but since I'm bootstrapping I don't see why it would have
to be defined ?
Here are the commands I typed to produce the bug report,
which I have gzipped and attached (unfortunately netscape
attachments don't get through, so
Jan Kort [mailto:[EMAIL PROTECTED]] writes:
Hi,
In ghc/Makefile it says:
17 # Order is important! driver/ has to come before
includes/ which
18 # again has to come before the rest.
19 #
20 # If we're booting from .hc files, swap the order
21 # we
37 matches
Mail list logo
