Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23907 - [ghc] Upgrade to binutils-2.21-6 breaks ghc 7.0.2

Attached to Project: Arch Linux
Opened by Vagif Verdi (vagif) - Saturday, 23 April 2011, 22:58 GMT
Last edited by Vesa Kaihlavirta (vegai) - Sunday, 26 June 2011, 19:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Vesa Kaihlavirta (vegai)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Upgrade to binutils-2.21-6 breaks ghc 7.0.2

Downgrading to binutils-2.21-4 fixes the problem.

Steps to reproduce:

remove .cabal and .ghc folders
cabal update
cabal install utf8-light

You will get the error.

This task depends upon

Closed by  Vesa Kaihlavirta (vegai)
Sunday, 26 June 2011, 19:10 GMT
Reason for closing:  Fixed
Comment by Allan McRae (Allan) - Saturday, 23 April 2011, 23:04 GMT
Can you post the actual error you are getting?
Comment by Vagif Verdi (vagif) - Saturday, 23 April 2011, 23:12 GMT
See attached file.
The actual error is: .size expression does not evaluate to a constant

I googled it and found this explanation:

http://us.generation-nt.com/answer/compile-error-arch-x86-kernel-entry-32-1422-error-size-expression-does-not-evaluate-constant-help-202586582.html

This lead me to realize that binutils was the culprit, so i downgraded it and that fixed the problem.
   error.txt (53.8 KiB)
Comment by Allan McRae (Allan) - Saturday, 23 April 2011, 23:20 GMT
  • Field changed: Summary (Upgrade to binutils-2.21-6 breaks ghc 7.0.2 → [ghc] Upgrade to binutils-2.21-6 breaks ghc 7.0.2)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Vesa Kaihlavirta (vegai)
Not a binutils bug as far as I am concerned. This appears to be ghc generating bad assembly code.
Comment by Stefan Husmann (stefanhusmann) - Wednesday, 11 May 2011, 20:38 GMT
A similar problem exists with assembler code generated by ocaml. See http://caml.inria.fr/mantis/view.php?id=5237 with a fix for ocaml. Maybe a similar fix can be found or created for ghc.
Comment by Allan McRae (Allan) - Wednesday, 11 May 2011, 20:42 GMT
I hear the ghc-7.0.3 update fixes this issue.

Loading...