Failed to bootstrap 6.10.4 with itself on Windows (MinGW)
leledumbo
leledumbo_cool at yahoo.co.id
Fri Jul 24 00:17:56 EDT 2009
OK, I've tried ghc's supplied gcc, too (not so easy, I need to set some
environment variables first) and here are the results:
With ghc's gcc:
D:/Sources/ghc/ghc-6.10.4/ghc/stage1-inplace/ghc.exe -package rts-1.0
-optc-O2 -
odir dist/build -c cbits/longlong.c -o dist/build/cbits/longlong.o
(echo dist/build/cbits/longlong.o `find dist/build -name "*_stub.o" -print`;
fin
d dist/build/GHC/Bool_split dist/build/GHC/Generics_split
dist/build/GHC/Orderin
g_split dist/build/GHC/PrimopWrappers_split dist/build/GHC/IntWord32_split
dist/
build/GHC/IntWord64_split dist/build/GHC/Tuple_split
dist/build/GHC/Types_split
dist/build/GHC/Unit_split -name '*.o' -print) | xargs c:/ghc/bin/ar.exe q
dist/
build/libHSghc-prim-0.1.0.0.a
xargs: c:/ghc/bin/ar.exe: Bad file number
make[2]: *** [dist/build/libHSghc-prim-0.1.0.0.a] Error 126
make[2]: Leaving directory `/d/Sources/ghc/ghc-6.10.4/libraries/ghc-prim'
make[1]: *** [make.library.ghc-prim] Error 2
make[1]: Leaving directory `/d/Sources/ghc/ghc-6.10.4/libraries'
make: *** [stage1] Error 2
With gcc 4.4.0:
d:/Sources/ghc/ghc-6.10.4/ghc/stage1-inplace/ghc -optc-O -optc-Wall -optc-W
-opt
c-Wstrict-prototypes -optc-Wmissing-prototypes -optc-Wmissing-declarations
-optc
-Winline -optc-Waggregate-return -optc-I../includes -optc-I. -optc-Iparallel
-op
tc-Ism -optc-DCOMPILING_RTS -optc-fomit-frame-pointer -optc-I../gmp/gmpbuild
-op
tc-I../libffi/build/include -optc-fno-strict-aliasing -fvia-C -static
-I../gmp
/gmpbuild -I../libffi/build/include -I. -dcmm-lint -hisuf thr_hi -hcsuf
thr_hc
-osuf thr_o -optc-DTHREADED_RTS -c Capability.c -o Capability.thr_o
Capability.c: In function 'giveCapabilityToTask':
Capability.c:257:0: error: cannot convert to a pointer type
make[2]: *** [Capability.thr_o] Error 1
make[1]: *** [all] Error 1
make[1]: Leaving directory `/d/Sources/ghc/ghc-6.10.4/rts'
make: *** [stage1] Error 2
> FYI, if you want your GHC build to work on Windows, it is best to use
> the same tools that we do
It's the same as using ghc's supplied gcc, right (other requirements from
the page already fulfilled)?
--
View this message in context: http://www.nabble.com/Failed-to-bootstrap-6.10.4-with-itself-on-Windows-%28MinGW%29-tp24599789p24638402.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at Nabble.com.
More information about the Glasgow-haskell-users
mailing list