any successfull ghc registerised builds on arm?

David Terei dave.terei at
Thu Jan 24 20:44:30 CET 2013

Hi all,

Can people please file bugs about these issues when they are confirmed
to some degree? Lots of ARM & LLVM stuff seems to just be floating
around mailing lists.... much higher chance of me or someone else
fixing if there are filed bug reports with test cases and/or patches

Austin and I also fixed a couple of LLVM related issues in the last 2
days or so, so hopefully that solved some of these.

Top level bugs to link to when filing other bugs please:

* GHC ARM support:
* LLVM Cross compilation:
* LLVM unregisterised issues:
* LLVM bootstrap issues:


On 24 January 2013 10:28, Nathan Hüsken <nathan.huesken at> wrote:
> On 01/24/2013 07:26 PM, Stephen Paul Weber wrote:
>> Somebody claiming to be Nathan Hüsken wrote:
>>> On 01/24/2013 07:00 PM, Stephen Paul Weber wrote:
>>>> Somebody claiming to be Karel Gardas wrote:
>>>>> On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
>>>> So, not sure on the right solution, but when I add   -lcaps    then the
>>>> linker errors go away and I can build executables.  Unfortunately, when
>>>> I try to run any of them on a device, I get a segfault, just as I always
>>>> did with registerised cross-builds for ARM... this with both llvm-3.0
>>>> and llvm-3.2
>>>> :(
>>> Can you run it in gdb and loock what the backtrace looks like?
>> [New pid 14037182 tid 1]
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x08502000 in ?? ()
>> (gdb) bt
>> #0  0x08502000 in ?? ()
>> #1  0x082ce4c4 in ?? ()
>> #2  0x082ce4c4 in ?? ()
>> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>> (gdb)
> Not very informative :).
> Did you compile with -debug?
> I remember I got a stack trace with gdb like this (when doing remote
> debugging) and got it cleaned up by loading the exectuable with "file".
> Maybe you have to do something like that to?
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at

More information about the Glasgow-haskell-users mailing list