Opened 9 years ago

Closed 9 years ago

#3037 closed bug (wontfix)

GHC panics when configuring base

Reported by: mooism Owned by:
Priority: normal Milestone:
Component: Compiler Version: 6.8.2
Keywords: Cc:
Operating System: Linux Architecture: x86
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


$ wget
--2009-02-19 19:54:31--
Connecting to||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 409339 (400K) [application/x-tar]
Saving to: `base-'

100%[========================================================================================================>] 409,339     86.7K/s   in 5.6s    

2009-02-19 19:54:37 (71.8 KB/s) - `base-' saved [409339/409339]

$ tar zxf base- 
$ cd base-
$ runhaskell Setup.hs configure

    attempting to use module `System.IO' (System/IO.hs) which is not loaded

<interactive>:1:22: Not in scope: `System.IO.stderr'

<interactive>:1:22: Not in scope: `System.IO.stdin'
ghc-6.8.2: panic! (the 'impossible' happened)
  (GHC version 6.8.2 for i386-unknown-linux):

Please report this as a GHC bug:

I am using Ubuntu 8.10 Linux 2.6.27-11-generic i686.

I am having trouble using cabal-install, and my real problem may lie there, but I thought I should report this anyway.

Change History (2)

comment:1 Changed 9 years ago by duncan

Keywords: base base- panic panic! removed

When cabal-install says a package cannot be installed because it needs base 4, that does not mean you should install base 4. It means you cannot use that version of that package with ghc-6.8. You either have to use an older version of the same package, avoid using the package or upgrade to ghc-6.10 which comes with base 4.

For exactly this reason, cabal-install does not decide to install base 4 (which is why you had to go to such lengths to try to install it).

comment:2 Changed 9 years ago by simonmar

difficulty: Unknown
Resolution: wontfix
Status: newclosed

The error message is no longer a panic in 6.10.1:

$ runhaskell Setup.hs configure
<command line>: module `Prelude' is not loaded

Though perhaps it's equally obscure. We don't plan to support this anyway.

Note: See TracTickets for help on using tickets.