Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#3506 closed bug (wontfix)

Can't compile 6.10.x from 6.8.3

Reported by: Pandarus Owned by:
Priority: normal Milestone:
Component: Compiler Version: 6.8.3
Keywords: Cc:
Operating System: Linux Architecture: x86_64 (amd64)
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Attempted compiles of 6.10.1, 6.10.3, and 6.10.4 all ended similarly.

Compile messages for attempted compile of 6.10.1 ended with:

[45 of 50] Compiling Distribution.Simple.GHC ( Distribution/Simple?/GHC.hs, dist-bootstrapping/build/Distribution/Simple/GHC.o )
[46 of 50] Compiling Distribution.Simple.Build ( Distribution/Simple/Build?.hs, dist-bootstrapping/build/Distribution/Simple/Build.o )
[47 of 50] Compiling Distribution.Simple.Haddock ( Distribution/Simple/Haddock?.hs, dist-bootstrapping/build/Distribution/Simple/Haddock.o )
[48 of 50] Compiling Distribution.Simple.Configure ( Distribution/Simple/Configure?.hs, dist-bootstrapping/build/Distribution/Simple/Configure.o )
[49 of 50] Compiling Distribution.Simple.Install ( Distribution/Simple/Install?.hs, dist-bootstrapping/build/Distribution/Simple/Install.o )
[50 of 50] Compiling Distribution.Simple ( Distribution/Simple?.hs, dist-bootstrapping/build/Distribution/Simple.o )
ghc-6.8.3: internal error: evacuate(static): strange closure type 1

(GHC version 6.8.3 for x86_64_unknown_linux)
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug

make[1]: * [bootstrapping.conf] Error 6
make[1]: Leaving directory `/home/dbridges/src/ghc-6.10.1/libraries'
make: * [stage1] Error 2

Change History (2)

comment:1 Changed 5 years ago by igloo

  • Difficulty set to Unknown
  • Resolution set to wontfix
  • Status changed from new to closed

The 6.8 branch is no longer being developed, so we won't be fixing this bug, I'm afraid. If you are unable to build a more recent GHC then you can download a binary distribution, or perhaps get a binary from your Linux distribution.

comment:2 Changed 5 years ago by simonmar

If the error is different each time, it may be that your hardware is faulty.

Note: See TracTickets for help on using tickets.