On Tue, Dec 2, 2014 at 5:58 PM, Joachim Breitner <mail@joachim-breitner.de> wrote:
Hi,


Am Sonntag, den 30.11.2014, 20:01 +0100 schrieb Joachim Breitner:
> I’m still seeing this failure:
>
> Compile failed (status 256) errors were:
> /tmp/ghc16123_0/ghc16123_5.s: Assembler messages:
>
> /tmp/ghc16123_0/ghc16123_5.s:26:0:
>      Error: can't resolve `.rodata' {.rodata section} - `Main_zdwwork_info$def' {.text section}
>
> /tmp/ghc16123_0/ghc16123_5.s:46:0:
>      Error: can't resolve `.rodata' {.rodata section} - `Main_work_info$def' {.text section}
>
> /tmp/ghc16123_0/ghc16123_5.s:66:0:
>      Error: can't resolve `.rodata' {.rodata section} - `Main_main1_info$def' {.text section}
>
> /tmp/ghc16123_0/ghc16123_5.s:86:0:
>      Error: can't resolve `.rodata' {.rodata section} - `Main_main_info$def' {.text section}
>
> /tmp/ghc16123_0/ghc16123_5.s:106:0:
>      Error: can't resolve `.rodata' {.rodata section} - `Main_main2_info$def' {.text section}
>
> /tmp/ghc16123_0/ghc16123_5.s:126:0:
>      Error: can't resolve `.rodata' {.rodata section} - `ZCMain_main_info$def' {.text section}
>
> *** unexpected failure for T5681(optllvm)
>
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/42557559/log.txt
>
> Any ideas?

is it possible that this is due the llvm version used? Do we support 3.4
in GHC HEAD?

   Using LLVM tools
      llc   : /usr/local/clang-3.4/bin/llc
      opt   : /usr/local/clang-3.4/bin/opt

This appears to affect all programs built with llvm-3.4. I filed a ticket (http://ghc.haskell.org/trac/ghc/ticket/9929).

Regards,
Reid Barton