Opened 16 years ago
Closed 15 years ago
#19574 closed defect (fixed)
ghc @6.10.2_0: gcc Internal error: Virtual timer expired (program cc1)
Reported by: | marco.comini@… | Owned by: | gwright@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.1 |
Keywords: | ghc internal gcc error | Cc: | gale@…, ryandesign (Ryan Carsten Schmidt) |
Port: | ghc |
Description
For the first time I've encountered a GCC internal error. Is it an already known issue or should I really report it to Apple?
Preprocessing library ghc-prim-0.1.0.0... Running Haddock for ghc-prim-0.1.0.0... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: rts-1.0 powerpc-apple-darwin8-gcc-4.0.1: Internal error: Virtual timer expired (program cc1) Please submit a full bug report. See <URL:http://developer.apple.com/bugreporter> for instructions. make[2]: *** [doc.library.ghc-prim] Error 1 make[1]: *** [stage2] Error 2 make: *** [bootstrap2] Error 2
Change History (9)
comment:1 Changed 16 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to gwright@… |
---|
comment:2 Changed 16 years ago by blair (Blair Zajac)
I'm using Xcode 2.5 and get the same error on an Intel 10.4 PowerMac.
I doubt we'll get a fix for this from Apple. Is there a way for the compile to use a newer gcc, say 4.3.3 from the gcc43 port?
I tried modifying Portfile. To the platform darwin 8 i386 variant, I added
depends_lib-append port:gcc43
and
configure.cc ${prefix}/bin/gcc-mp-4.3
but that didn't help, it still picked up /usr/bin/gcc somewhere.
comment:3 Changed 16 years ago by gale@…
I get the same issue on an Intel MacBook, Mac OS X 10.4.11, XCode 2.5.
So "PPC" should probably be removed from the title of this bug.
comment:5 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Summary: | GHC 6.10.2_0 (PPC MacOS 10.4) GCC internal error → ghc @6.10.2_0: gcc Internal error: Virtual timer expired (program cc1) |
My ghc build stops at the same place, on Mac OS X 10.4.11 PowerPC with Xcode 2.5, except that these two lines are not present in my output:
powerpc-apple-darwin8-gcc-4.0.1: Internal error: Virtual timer expired (program cc1) Please submit a full bug report. See <URL:http://developer.apple.com/bugreporter> for instructions.
That is to say, my output ends with:
Preprocessing library ghc-prim-0.1.0.0... Running Haddock for ghc-prim-0.1.0.0... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: rts-1.0 make[2]: *** [doc.library.ghc-prim] Error 1 make[1]: *** [stage2] Error 2 make: *** [bootstrap2] Error 2 Error: Unable to upgrade port: 1
That's when trying to upgrade to 6.10.2_0 while 6.10.1_8 is installed and active. If I deactivate 6.10.1_8, clean and try again, the output ends with:
/mp/var/macports/build/_Volumes_data_macports_ports_lang_ghc/work/ghc-bootstrap/bin/ghc -#include cutils.h -DSTAGE=1 -package-name ghc-6.10.2 -hide-all-packages -no-user-package-conf -package-conf /mp/var/macports/build/_Volumes_data_macports_ports_lang_ghc/work/ghc-6.10.2/libraries/bootstrapping.conf -i -idist-stage1/build -inativeGen -ibasicTypes -icmm -icodeGen -icoreSyn -icprAnalysis -ideSugar -ighci -ihsSyn -iiface -imain -iparser -iprelude -iprofiling -irename -isimplCore -isimplStg -ispecialise -istgSyn -istranal -itypecheck -itypes -iutils -ivectorise -idist-stage1/build/autogen -Idist-stage1/build/autogen -Idist-stage1/build -Istage1 -I../libraries/base/cbits -I../libraries/base/include -I. -Iparser -Iutils -optP-include -optPdist-stage1/build/autogen/cabal_macros.h -odir dist-stage1/build -hidir dist-stage1/build -stubdir dist-stage1/build -package Cabal-1.6.0.3 -package array-0.2.0.0 -package base-4.0.0.0 -package bytestring-0.9.1.4 -package containers-0.2.0.0 -package directory-1.0.0.2 -package filepath-1.1.0.2 -package haskell98-1.0.1.0 -package hpc-0.5.0.3 -package old-time-1.0.0.1 -package process-1.0.1.0 -package unix-2.3.1.0 -O -Wall -fno-warn-name-shadowing -fno-warn-orphans -XCPP -XMagicHash -XUnboxedTuples -XPatternGuards -XForeignFunctionInterface -XEmptyDataDecls -XTypeSynonymInstances -XMultiParamTypeClasses -XFlexibleInstances -XRank2Types -XScopedTypeVariables -XDeriveDataTypeable -idist-stage1/build -H32m -O -I/mp/include -L/mp/lib -Rghc-timing -c simplCore/SimplMonad.lhs -o dist-stage1/build/SimplMonad.o -ohi dist-stage1/build/SimplMonad.hi <<ghc: 211331804 bytes, 15 GCs, 6348690/12508060 avg/max bytes residency (2 samples), 38M in use, 0.03 INIT (0.00 elapsed), 3.60 MUT (8.56 elapsed), 1.11 GC (2.93 elapsed) :ghc>> make[2]: *** [dist-stage1/build/SimplMonad.o] Error 1 make[1]: *** [build.stage.1] Error 2 make: *** [stage1] Error 1
which doesn't really look like much of an error to me, but it stops there.
Grepping the entire debug output for "Warning" I do see this; not sure if it's relevant:
Configuring ghc-6.10.2... Warning: 'include-dirs: ../libraries/base/cbits' is a relative path outside of the source tree. This will not work when generating a tarball with 'sdist'. Warning: 'include-dirs: ../libraries/base/include' is a relative path outside of the source tree. This will not work when generating a tarball with 'sdist'. Warning: This package indirectly depends on multiple versions of the same package. This is highly likely to cause a compile failure. package process-1.0.1.0 requires filepath-1.1.0.1 package directory-1.0.0.2 requires filepath-1.1.0.1 package ghc-6.10.2 requires filepath-1.1.0.2 package Cabal-1.6.0.3 requires filepath-1.1.0.2
comment:6 Changed 15 years ago by gale@…
comment:7 follow-up: 8 Changed 15 years ago by gwright@…
Status: | new → assigned |
---|
6.10.3 now includes a patch that should fix the main problem described here. It is included in the current revision 4.
comment:8 Changed 15 years ago by marco.comini@…
Replying to gwright@…:
6.10.3 now includes a patch that should fix the main problem described here. It is included in the current revision 4.
Yes, now it worked fine. At least for me :)
comment:9 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Presumed fixed; closing.
If you are using Xcode 2.5, then yes, you should report it to Apple. Otherwise try upgrading first.