Opened 4 years ago

Closed 4 years ago

#10329 closed bug (fixed)

ghc-7.10 is configured to use llvm-3.6 but only compiles with llvm-3.5

Reported by: erikd Owned by:
Priority: normal Milestone: 7.10.2
Component: Compiler Version: 7.10.1
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Building GHC failed Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s): Phab:D856
Wiki Page:


Commit 07da52ce2db1 on the ghc-7.10 branch cherry picks commit 42448e3757f2 from the git master branch, but that commit checks for and insists on using llvm version 3.6. However, the code in the ghc-7.10 branch is not compatible with llvm-3.6.

The attatched patch changes the requirement to be for llvm-3.5 and is the ghc-7.10 version of commit 485dba86d2519c in the master branch.

Attachments (1)

0001-configure-LLVM-and-LD-detection-improvements-10329.patch (5.7 KB) - added by erikd 4 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 4 years ago by erikd

Status: newpatch

comment:2 Changed 4 years ago by erikd

Differential Rev(s): Phab:D856

comment:3 Changed 4 years ago by erikd

The current ghc-7.10 branch fails to build with BuldFlavour = perf-llvm due to:

/usr/bin/opt-3.6: /tmp/ghc31615_0/ghc31615_2.ll:7:6: error: unexpected type in
metadata definition
!0 = metadata !{metadata !"top", i8* null}

which is a direct result of the issue in this ticket and which the patch in Phab:D856 fixes.

Last edited 4 years ago by erikd (previous) (diff)

comment:4 Changed 4 years ago by erikd

Resolution: fixed
Status: patchclosed

This was fixed in commit:

commit 99e4e26a2672f7697cf1f76306c3dfb63125e035
Author: Erik de Castro Lopo <>
Date:   Sat Apr 25 08:14:48 2015 +0200

    configure: LLVM and LD detection improvements (#10329)
    The ghc-7.10 branch *only* works with llvm-3.5.
    This commit is basically the ghc-7.10 branch version of
    485dba86d2 in the master branch.
    Signed-off-by: Erik de Castro Lopo <>
    Differential Revision:
Note: See TracTickets for help on using tickets.