Version 9 (modified by guest, 9 years ago) (diff)


GHC port for arm-unknown-linux-gnu

My goal is to create a registerised port of GHC to the nokia 770.


There is currently an unregisterised build available for Maemo 1.x. This project is temporarily on hold while two big transitions take place:

  1. Maemo 2.0 supports the new EABI standard which affects a bunch of things (done) (for more info see )
  2. GHC 6.6 release (soon)

Setting up the build environment

I have been using the standard maemo cross-development environment. Instructions for setting up this environment can be found here:

Changes to standard procedure

The updated instructions on this page should now work:

With two small changes:

(1) I had to add --srcdir=.

Anyplace configure is called I get this error:

This configuration does not support the `--srcdir' option..

Adding --srcdir=. makes the error go away.

(2) ghc/Makefile SUBDIRS ordering

This has been fixed in head, but if you download the 6.4.2 release you will need to edit ghc/Makefile and change the ordering of the SUBDIRS so that lib comes before compiler.

This is the default ordering:

ifeq "$(BootingFromHc)" "YES"
SUBDIRS = includes rts docs compiler lib utils driver

and you want

ifeq "$(BootingFromHc)" "YES"
SUBDIRS = includes rts docs lib compiler utils driver

That should get to the point of having a ghc-inplace built.

NOTE: if you try to move the directory to a new location or name, the inplace compiler will stop working because it has absolute paths hard coded to the current location.

Build ghc using ghc-inplace

(1) unroll the ghc source tarball into a new directory.

(2) ./configure --srcdir=. --with-ghc=/abs/path/to/ghc-inplace

(3) create a mk/ with these two lines:

GhcUnregisterised = YES
GhcWithNativeCodeGen = NO

(4) make

(5) make install

I think there may have been one other step in there somewhere...

This should build and install ghc. Unfortunately, the floating point code will be broken.

Run the test suite

(1) get the testsuite that corresponds to your release, for example:

(2) untar it in the ghc-6.4.2 directory.

(3) edit mk/ and change the -e config.time_prog line to:

        -e config.timeout_prog=\"\" \

I had to do this because the timeout program interacted badly with the scratchbox shell causing all the tests to timeout and fail.

(4) cd to test/ghc-regress

(5) make TEST_HC=ghc fast


(5) make TEST_HC=ghc # for a longer test

Step By Step Porting to Maemo 2.0

T & H

tar -xvjf ghc-6.6-src.tar.bz2
cd ghc-6.6

$ ./configure --enable-hc-boot --enable-hc-boot-unregisterised --srcdir=.
$ cd includes
$ make

$ ./configure --srcdir=.

Create H/mk/, with the following contents:


GhcUnregisterised = YES
GhcLibHcOpts = -O -fvia-C -keep-hc-files
GhcRtsHcOpts = -keep-hc-files
GhcLibWays =
SplitObjs = NO
GhcWithNativeCodeGen = NO
GhcWithInterpreter = NO
GhcStage1HcOpts = -O
GhcStage2HcOpts = -O -fvia-C -keep-hc-files
SRC_HC_OPTS += -H32m
GhcBootLibs = YES

Change Target* and TARGET* variables in H/mk/


TARGETPLATFORM			= arm-unknown-linux

TargetPlatform_CPP		= arm_unknown_linux
TargetArch_CPP			= arm

arm_unknown_linux_TARGET       = 1
arm_TARGET_ARCH      = 1

Copy T/ghc/includes/ghcautoconf.h, T/ghc/includes/DerivedConstants.h, and T/ghc/includes/GHCConstants.h to H/ghc/includes. Note that we are building on the host machine, using the target machine's configuration files. This is so that the intermediate C files generated here will be suitable for compiling on the target system.

Touch the generated configuration files, just to make sure they don't get replaced during the build:


$ cd H/ghc/includes
$ touch ghcautoconf.h DerivedConstants.h GHCConstants.h mkDerivedConstants.c
$ touch mkDerivedConstantsHdr mkDerivedConstants.o mkGHCConstants mkGHCConstants.o