Unregistered build (was Re: AMD64)

Simon Marlow simonmar at microsoft.com
Tue Jun 15 06:55:13 EDT 2004


On 14 June 2004 21:57, Gerd M wrote:

> Well I just tried it and that's what happened:
>
------------------------------------------------------------------------
> ==fptools== make boot - --no-print-directory -r;
> in ghc-6.2.1/ghc/utils/ghc-pkg
>
------------------------------------------------------------------------
> ghc-test/usr/bin/ghc -M -optdep-f -optdep.depend  -osuf o    -H16m -O
> -cpp -DPKG_TOOL -DWANT_PRETTY -DGHC_PKG_VERSION=6.2.1 Main.hs
> Package.hs ParsePkgConfLite.hs
> Main.hs:87: warning: backslash and newline separated by space
> Main.hs:259: warning: backslash and newline separated by space
> Main.hs:260: warning: backslash and newline separated by space
> make all
> ghc-test/usr/bin/ghc -H16m -O -cpp -DPKG_TOOL -DWANT_PRETTY
> -DGHC_PKG_VERSION=6.2.1    -c Main.hs -o Main.o  -ohi Main.hi
> Main.hs:87: warning: backslash and newline separated by space
> Main.hs:259: warning: backslash and newline separated by space
> Main.hs:260: warning: backslash and newline separated by space
> Main.hs:87: lexical error in string/character literal
> make[4]: *** [Main.o] Error 1
> make[3]: *** [boot] Error 2
> make[2]: *** [boot] Error 1
> make[1]: *** [boot] Error 1
> make[1]: Leaving directory `ghc-6.2.1/ghc'

This is caused by changes to CPP in recent versions of gcc.
Unfortunately it means we can't use string gaps in CPP'd source any
more.  Until we move to cpphs, I'll have to remove all string gaps from
our sources.  Sigh.

Cheers,
	Simon


More information about the Glasgow-haskell-users mailing list