On Mon, 21 Jan 2013, rocon...@theorem.ca wrote:
On Mon, 21 Jan 2013, Karel Gardas wrote:
On 01/21/13 12:49 AM, rocon...@theorem.ca wrote:
On Sun, 20 Jan 2013, Karel Gardas wrote:
Okay, I patched the settings filed generted by ./configure in the
binary-dist and rank make install which
FYI, I created a wiki page for cross-compiling to Raspberry Pi:
http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation/RaspberryPi
I have an unregisterised build using LLVM working now (it just worked,
modulo the tiny fix for #7622).
Cheers,
Simon
On 21/01/13 16:06, Karel
Simon
Looking at the wiki - I take it that the stage 1 compiler can now be used as
native compiler on the RPi? (last line of entry)?
Neil
On 25 Jan 2013, at 10:46, Simon Marlow marlo...@gmail.com wrote:
FYI, I created a wiki page for cross-compiling to Raspberry Pi:
On 25/01/13 11:23, Neil Davies wrote:
Simon
Looking at the wiki - I take it that the stage 1 compiler can now be used as
native compiler on the RPi? (last line of entry)?
Do you mean the stage 2 compiler? If so yes - in principle. But in
practice the binary-dist machinery doesn't work
That's good to hear - we've got AFS and the dev-RPi's are using it…
Neil
On 25 Jan 2013, at 12:20, Simon Marlow marlo...@gmail.com wrote:
On 25/01/13 11:23, Neil Davies wrote:
Simon
Looking at the wiki - I take it that the stage 1 compiler can now be used as
native compiler on the RPi?
On Mon, 21 Jan 2013, Karel Gardas wrote:
On 01/21/13 12:49 AM, rocon...@theorem.ca wrote:
On Sun, 20 Jan 2013, Karel Gardas wrote:
Okay, I patched the settings filed generted by ./configure in the
binary-dist and rank make install which completed. However,
pi@raspberrypi /tmp/bindist $
On 01/21/13 04:43 PM, rocon...@theorem.ca wrote:
So the binary-dist has a settings.in file. It is the configure step in
the binary-dist that generates the corrupt settings file.
Perhaps you've forgotten to regenerate bin-dist configure as you did
with build tree configure after applying my
On Wed, 16 Jan 2013, Karel Gardas wrote:
You should not IMHO. My patch should solve all your issues. :-) The only
issue you may get is that your distro ghc will compile for soft-float ABI and
your compiled GHC will compile to hard-float and object files will get mixed
somewhere. But I trust
On 01/20/13 07:17 PM, rocon...@theorem.ca wrote:
On Wed, 16 Jan 2013, Karel Gardas wrote:
You should not IMHO. My patch should solve all your issues. :-) The
only issue you may get is that your distro ghc will compile for
soft-float ABI and your compiled GHC will compile to hard-float and
On Sun, 20 Jan 2013, Karel Gardas wrote:
On 01/20/13 07:17 PM, rocon...@theorem.ca wrote:
On Wed, 16 Jan 2013, Karel Gardas wrote:
You should not IMHO. My patch should solve all your issues. :-) The
only issue you may get is that your distro ghc will compile for
soft-float ABI and your
On 01/20/13 07:50 PM, rocon...@theorem.ca wrote:
Karel, maybe you should try deploying a binary-dist on your panda board?
Sorry? What's binary-dist? And why I should do that? And what
exactly do you mean by deploying? And on what OS? Ubuntu or Raspbian
run in Ubuntu chroot?
What I'm
On Sun, 20 Jan 2013, Karel Gardas wrote:
On 01/20/13 07:50 PM, rocon...@theorem.ca wrote:
Karel, maybe you should try deploying a binary-dist on your panda board?
Sorry? What's binary-dist? And why I should do that? And what
exactly do you mean by deploying? And on what OS? Ubuntu or
On Sun, 20 Jan 2013, Karel Gardas wrote:
On 01/20/13 07:17 PM, rocon...@theorem.ca wrote:
On Wed, 16 Jan 2013, Karel Gardas wrote:
You should not IMHO. My patch should solve all your issues. :-) The
only issue you may get is that your distro ghc will compile for
soft-float ABI and your
On 01/20/13 08:27 PM, rocon...@theorem.ca wrote:
Looks like you do have corrupted settings file. Recover it by adding
HARD following armABI = , so result should be:
ArchARM {armISA = ARMv6, armISAExt = [VFPv2], armABI = HARD}
Okay, I patched the settings filed generted by ./configure in the
On Sun, 20 Jan 2013, Karel Gardas wrote:
On 01/20/13 08:27 PM, rocon...@theorem.ca wrote:
Looks like you do have corrupted settings file. Recover it by adding
HARD following armABI = , so result should be:
ArchARM {armISA = ARMv6, armISAExt = [VFPv2], armABI = HARD}
Okay, I patched the
On Sun, 20 Jan 2013, Karel Gardas wrote:
On 01/20/13 08:27 PM, rocon...@theorem.ca wrote:
Looks like you do have corrupted settings file. Recover it by adding
HARD following armABI = , so result should be:
ArchARM {armISA = ARMv6, armISAExt = [VFPv2], armABI = HARD}
Okay, I patched the
On 01/21/13 12:49 AM, rocon...@theorem.ca wrote:
On Sun, 20 Jan 2013, Karel Gardas wrote:
Okay, I patched the settings filed generted by ./configure in the
binary-dist and rank make install which completed. However,
pi@raspberrypi /tmp/bindist $ bin/ghc --make Main.hs
[1 of 1] Compiling Main
On Thu, 17 Jan 2013, rocon...@theorem.ca wrote:
On Thu, 17 Jan 2013, Austin Seipp wrote:
There have been a few of these bugs recently it seems. If you could:
use the stage1 compiler to compile a simple executable, like 'main =
return ()' or hello world or whatever.
The stage1 compiler can be
On 01/18/13 05:49 PM, rocon...@theorem.ca wrote:
I don't know much about gdb, but
$ /usr/bin/gdb /tmp/Main
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free
On Fri, 18 Jan 2013, Karel Gardas wrote:
On 01/18/13 05:49 PM, rocon...@theorem.ca wrote:
I don't know much about gdb, but
$ /usr/bin/gdb /tmp/Main
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
On Wed, 16 Jan 2013, Karel Gardas wrote:
On 01/16/13 08:12 PM, rocon...@theorem.ca wrote:
On Wed, 16 Jan 2013, Karel Gardas wrote:
Good! So the patch I already provided is working fine at least w.r.t.
change in configure. I've tested it here on my raspbian chroot on
pandaboard where I've
There have been a few of these bugs recently it seems. If you could:
use the stage1 compiler to compile a simple executable, like 'main =
return ()' or hello world or whatever.
The stage1 compiler can be located in the build directory, under
'inplace/bin/ghc-stage1'. So something like:
GHC
On Thu, 17 Jan 2013, Austin Seipp wrote:
There have been a few of these bugs recently it seems. If you could:
use the stage1 compiler to compile a simple executable, like 'main =
return ()' or hello world or whatever.
The stage1 compiler can be located in the build directory, under
Guys,
I've installed raspbian into ubuntu chroot on my panda. Now to simulate
what GHC detects on your hardware, could you be so kind and send me
output of:
uname -m
uname -r
uname -s
uname -v
this looks like a needed info for config.guess to detect machine
hardware well.
Also if you
I looked at that route - the issue is that the emulator only has 256M of RAM
(and that's not changeable) - so there are going to be build issues with the
GHC tool chain - it was then that I moved to real hardware.
Neil
On 15 Jan 2013, at 17:01, rocon...@theorem.ca wrote:
On Tue, 15 Jan 2013,
Ok - I'll put up a machine in a DMZ sometime later today (RPi just arrived by
post) .
I'll make it available on an non-standard ssh port - I suggest access via
ssh-key only.
If you want to email me the appropriate line for .ssh/authorizedkeys please do.
If you want to encrypt it with gpg,
On Wed, 16 Jan 2013, Karel Gardas wrote:
Guys,
I've installed raspbian into ubuntu chroot on my panda. Now to simulate what
GHC detects on your hardware, could you be so kind and send me output of:
uname -m
armv6l
uname -r
3.6.11+
uname -s
Linux
uname -v
#346 PREEMPT Fri Dec
Good! So the patch I already provided is working fine at least w.r.t.
change in configure. I've tested it here on my raspbian chroot on
pandaboard where I've hacked config.guess to print exactly what you get
on real rpi.
Now, I'm curious if the hack in DriverPipeline.hs helps too.
Were you
On Wed, 16 Jan 2013, Karel Gardas wrote:
Good! So the patch I already provided is working fine at least w.r.t. change
in configure. I've tested it here on my raspbian chroot on pandaboard where
I've hacked config.guess to print exactly what you get on real rpi.
Now, I'm curious if the hack
On 01/16/13 08:12 PM, rocon...@theorem.ca wrote:
On Wed, 16 Jan 2013, Karel Gardas wrote:
Good! So the patch I already provided is working fine at least w.r.t.
change in configure. I've tested it here on my raspbian chroot on
pandaboard where I've hacked config.guess to print exactly what you
On Mon, 14 Jan 2013, Thijs Alkemade wrote:
Op 14 jan. 2013, om 17:30 heeft rocon...@theorem.ca het volgende geschreven:
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case of
ARMv6/ARM11 chip here...
I'm afraid LLVM is not well
Op 15 jan. 2013, om 17:36 heeft rocon...@theorem.ca het volgende geschreven:
Okay, I tried:
SRC_HC_OPTS= -H64m -Rghc-timing -optc-mfloat-abi=hard
-optc-march=armv6 -optc-mfpu=vfp -optlc=-mattr=+vfp2
GhcStage1HcOpts= -O -fllvm
GhcStage2HcOpts= -O0 -fllvm
GhcLibHcOpts
Hi - would another RPi (or even 2 from tomorrow another one arriving) help?
I can make them accessible (i.e. in our DMZ) -
Neil
On 15 Jan 2013, at 16:36, rocon...@theorem.ca wrote:
On Mon, 14 Jan 2013, Thijs Alkemade wrote:
Op 14 jan. 2013, om 17:30 heeft rocon...@theorem.ca het volgende
On Tue, 15 Jan 2013, Thijs Alkemade wrote:
Op 15 jan. 2013, om 17:36 heeft rocon...@theorem.ca het volgende geschreven:
Okay, I tried:
SRC_HC_OPTS= -H64m -Rghc-timing -optc-mfloat-abi=hard -optc-march=armv6
-optc-mfpu=vfp -optlc=-mattr=+vfp2
GhcStage1HcOpts= -O -fllvm
In theory we could try a couple variations of builds at the same time.
But at the moment, I'm running low on ideas on what to try.
I just got the, extensive, raspbian patches for 7.4.1 and I'm going to
browse through them when I get time (apt-get source ghc).
On Tue, 15 Jan 2013, Neil Davies
Well, if you make some board available in DMZ I'm certainly interested
to run at least configure on it from GHC HEAD to see what we need to
hack in order to add support for RPi into GHC HEAD.
Unfortunately GHC HEAD is now in a wrong state w.r.t. LLVM based build,
but Austin is working on
rocon...@theorem.ca writes:
Okay, I tried:
SRC_HC_OPTS= -H64m -Rghc-timing -optc-mfloat-abi=hard
-optc-march=armv6 -optc-mfpu=vfp -optlc=-mattr=+vfp2
GhcStage1HcOpts= -O -fllvm
GhcStage2HcOpts= -O0 -fllvm
GhcLibHcOpts = -O -fllvm -optlc-float-abi=hard
and I got the
Well, just wild guessing what's needed on RPi, but could you who do have
this board attempt to use attached patch? Don't forget to ./boot as this
change configure. Also testing it on completely clean tree may be wise
idea. Also after configure run please check that you do have VFPv2 in
the
Op 15 jan. 2013, om 18:16 heeft Karel Gardas karel.gar...@centrum.cz het
volgende geschreven:
Well, if you make some board available in DMZ I'm certainly interested to run
at least configure on it from GHC HEAD to see what we need to hack in order
to add support for RPi into GHC HEAD.
On 01/15/13 08:56 PM, Thijs Alkemade wrote:
Op 15 jan. 2013, om 18:16 heeft Karel Gardaskarel.gar...@centrum.cz het
volgende geschreven:
Well, if you make some board available in DMZ I'm certainly interested to run
at least configure on it from GHC HEAD to see what we need to hack in order
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case of
ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so kind and
test if adding -optlc=-mattr=+vfp2 helps? You need to add it to your
Hi
I've found myself wanting to get GHC 7.4.2 (need TemplateHaskell for something)
working on the rapberry pi - can you (or anyone out there) share where you are
at?
My starting point is the raspian image of 2012-12-18-wheezy-raspian that has
GHC 7.4.1 on it...
Neil
On 11 Jan 2013, at
I've tried to build 6.12.3, 7.4.1, 7.4.2, and 7.6.1, with a few various
patches, and I'm stuck in the final stage with errors like:
/usr/bin/ld: error: libraries/ghc-prim/dist-install/build/cbits/debug.o uses
VFP register arguments,
libraries/ghc-prim/dist-install/build/HSghc-prim-0.3.0.0.o
If there is anything useful I can do - shout.
Given the time it takes to do each rebuild on a raspberry pi - this is real
dedication!
Neil
On 12 Jan 2013, at 17:01, rocon...@theorem.ca wrote:
I've tried to build 6.12.3, 7.4.1, 7.4.2, and 7.6.1, with a few various
patches, and I'm stuck in
Karel Gardas karel.gar...@centrum.cz writes:
On 01/11/13 09:25 PM, rocon...@theorem.ca wrote:
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case
of ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case of
ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so kind and
test if adding -optlc=-mattr=+vfp2 helps? You need to add it to your
On Sat, 12 Jan 2013, rocon...@theorem.ca wrote:
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case of
ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so kind and
test if adding
What version of GHC did you build?
On Sat, 12 Jan 2013, Ben Gamari wrote:
Karel Gardas karel.gar...@centrum.cz writes:
On 01/11/13 09:25 PM, rocon...@theorem.ca wrote:
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case
of
rocon...@theorem.ca writes:
What version of GHC did you build?
This was building from the ghc-7.4 branch. That being said, after this
build finished I noticed that the resulting stage 2 compiler wasn't
invoking llc with the correct parameters, resulting in the same linker
error when doing
On Sat, 12 Jan 2013, Ben Gamari wrote:
rocon...@theorem.ca writes:
What version of GHC did you build?
This was building from the ghc-7.4 branch. That being said, after this
build finished I noticed that the resulting stage 2 compiler wasn't
invoking llc with the correct parameters,
rocon...@theorem.ca writes:
On Sat, 12 Jan 2013, Ben Gamari wrote:
SRC_HC_OPTS= -H64m -Rghc-timing
GhcStage1HcOpts= -O -fvia-C
GhcStage2HcOpts= -O0 -fllvm -keep-llvm-files -debug -DDEBUG
-optc-mfloat-abi=hard -optc-mcpu=cortex-a9 -optlc-float-abi=hard
On Sat, Jan 12, 2013 at 10:23 PM, rocon...@theorem.ca wrote:
GhcLibHcOpts = -O -fllvm -optc-mfloat-abi=hard -optc-mcpu=cortex-a9
-optlc-float-abi=hard -optlc-mcpu=cortex-a9
You've written -optc-mfloat-abi=hard -optc-mcpu=cortex-a9 twice in your
GhcLibHcOpts.
Not quite. Notice
On Sat, Jan 12, 2013 at 10:29 PM, Austin Seipp mad@gmail.com wrote:
The first one passes the options onto LLVM's code generator tool,
'llc', so it also gets the ABI options right.
s/first/second/
--
Regards,
Austin
___
Glasgow-haskell-users
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case of
ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so kind and
test if adding -optlc=-mattr=+vfp2 helps? You need to add it to your
On 01/11/13 09:25 PM, rocon...@theorem.ca wrote:
On Thu, 10 Jan 2013, Karel Gardas wrote:
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case
of ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so
kind and test if adding
Hmm, are you using Raspbian? I.e. hard-float abi caught my eye in case
of ARMv6/ARM11 chip here...
I'm afraid LLVM is not well guided in your case so could you be so kind
and test if adding -optlc=-mattr=+vfp2 helps? You need to add it to your
build.mk probably and you will need to rebuild
Thanks for the advice; However, it had little effect.
I now have the errors:
===--- building final phase
make -r --no-print-directory -f ghc.mk phase=final all
LD libraries/ghc-prim/dist-install/build/HSghc-prim-0.3.0.0.o
/usr/bin/ld: error:
Hi,
find ghc's generated settings file. What FPU is used there?
Thanks,
Karel
On 01/ 9/13 09:47 PM, rocon...@theorem.ca wrote:
Thanks for the advice; However, it had little effect.
I now have the errors:
===--- building final phase
make -r --no-print-directory -f ghc.mk phase=final all
LD
This is the settingings file:
$ cat settings
[(GCC extra via C opts, -fwrapv),
(C compiler command, /usr/bin/gcc),
(C compiler flags, -fno-stack-protector -Wl,--hash-size=31
-Wl,--reduce-memory-overheads),
(ar command, /usr/bin/ar),
(ar flags, q),
(ar supports at file, YES),
(touch
Op 8 jan. 2013, om 05:16 heeft rocon...@theorem.ca het volgende geschreven:
On Thu, 3 Jan 2013, Thijs Alkemade wrote:
I believe I had the same problem, which disappeared after upgrading llvm
from 3.0 to 3.1, and using that instead for ./configure.
Hope this helps,
Thijs
Thanks,
On Thu, 3 Jan 2013, Thijs Alkemade wrote:
I believe I had the same problem, which disappeared after upgrading llvm from
3.0 to 3.1, and using that instead for ./configure.
Hope this helps,
Thijs
Thanks, using LLVM 3.1 seems to have improved the siutation, but I'm
running into a new error.
(Sorry, forgot to CC the list)
Original Message
From: Thijs Alkemade m...@thijsalkema.de
Sent: Thu Jan 03 10:31:50 CET 2013
To: rocon...@theorem.ca
Subject: Re: Error building ghc on raspberry pi.
rocon...@theorem.ca wrote:
Some further information it seems that llc
rocon...@theorem.ca writes:
Some further information it seems that llc is segfaulting:
Where did you get your LLVM build from? Did you try running the LLVM
testsuite? IIRC, LLVM 3.0 was less than stellar on ARM.
- Ben
___
Glasgow-haskell-users
My random guess is that /tmp is mounted using tmpfs (aka a RAM drive)
and it got full. Try remounting /tmp to use the sdcard instead ?
On Wed, Jan 2, 2013 at 7:32 PM, rocon...@theorem.ca wrote:
I'm trying to build ghc-7.4.1 using ghc-7.4.1 on my raspberry pi (armv6l)
and I get the following
Thanks for your help, but unfortunately this isn't the issue
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 924G 584G 294G 67% /tmp
So there is pleanty of room on temp.
BTW, I also tried building it twice and I got the same error at the same
place.
On Wed, 2 Jan 2013,
Some further information it seems that llc is segfaulting:
pi@raspberrypi /tmp/ghc-7.4.1 $ llc -O3 -relocation-model=static /tmp/ghc7189_0/ghc7189_0.bc -o /tmp/ghc7189_0/ghc7189_0.lm_s
Stack dump:
0. Program arguments: llc -O3 -relocation-model=static /tmp/ghc7189_0/ghc7189_0.bc -o
66 matches
Mail list logo
