#3060: impossible internal bug while building darcs
-------------------------+--------------------------------------------------
    Reporter:  quick     |        Owner:          
        Type:  bug       |       Status:  reopened
    Priority:  normal    |    Milestone:          
   Component:  Compiler  |      Version:  6.10.1  
    Severity:  minor     |   Resolution:          
    Keywords:            |   Difficulty:  Unknown 
    Testcase:            |           Os:  Linux   
Architecture:  x86       |  
-------------------------+--------------------------------------------------
Changes (by quick):

  * status:  closed => reopened
  * resolution:  invalid =>
  * severity:  major => minor

Comment:

 Sorry for the delay...

 I can confirm that a cabal-based installation of unix-2.3.1.0 causes the
 darcs-build error to re-occur.  The build of unix-2.3.1.0 proceeded
 without problems, but the result is fatal.

 A {{{ghc-pkg hide unix-2.3.1.0}}} is successful and a list confirms that
 unix is hidden (surrounded by parentheses) but the error persists.

 I cannot {{{ghc-pkg unregister unix}}} because:
 {{{
 ghc-pkg: unregistering unix would break the following packages:
 haddock-2.3.0 ghc-6.10.1 directory-1.0.0.2 process-1.0.1.0 hpc-0.5.0.2
 Cabal-1.6.0.1 haskell98-1.0.1.0 (use --force to override)
 }}}

 The only solution apparent at this point is to remove GHC-6.10.1 and
 fallback to GHC-6.8.3, then use GHC-6.8.3 to rebuild and re-install
 GHC-6.10.1.  I cannot simply rebuild GHC-6.10.1 because it has a similar
 failure attempting to build itself.

 So... I'm going to re-open this bug, but with lower severity (because
 there are workarounds).  The unix package is definitely problematic post-
 install.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3060#comment:8>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to