BUG: ghc-6.2.2 does not build on 10.2.8

[furr@…]

It appears that there are several problems with the ghc port under 10.2.

• The bootstrapped ghc binary needs readline-4
• The Portfile provides an incorrect parameter for the compiler:

"gcc3 -E traditional-cpp" should be "gcc3 -E -traditional-cpp" (multiple occurences)

• The build itself fails:

[...] ==fptools== make boot - --no-print-directory -r;

in /opt/dports/darwinports/dports/lang/ghc/work/ghc-6.2.2/ghc/utils/ghc-pkg

---

/bin/sh: test: unknownunknown: integer expression expected /opt/dports/darwinports/dports/lang/ghc/work/ghc-bootstrap/bin/ghc -pgmP "gcc3 -E - traditional-cpp" -M -optdep-f -optdep.depend -osuf o -H16m -O -I/opt/dportsinclude -L/ opt/dportslib -pgmP "gcc3 -E -traditional-cpp" -cpp -DPKG_TOOL -DWANT_PRETTY -package lang -package util -package text Main.hs Package.hs ParsePkgConfLite.hs Version.hs Main.hs:163:31: missing terminating ' character Main.hs:274:36: missing terminating ' character Main.hs:275:30: missing terminating ' character Main.hs:518:7: missing terminating ' character make[3]: * [depend] Error 1 make[2]: * [boot] Error 1 make[1]: * [boot] Error 1 make: * [build] Error 1

The test error occurs because configure can't detect the version of ghc. It tries to invoke ghc as

'/opt/dports/darwinports/dports/lang/ghc/work/ghc-bootstrap/bin/ghc -pgmP "gcc3 -E

-traditional-cpp"' which fails because this is treated as a single filename rather than a filename + arguments. However, after manually setting the version in the makefile, the same parse error occurs.

[gwright@…]

I'll take a look at this. I may need the help of someone who still runs 10.2 (Jaguar) to test.

[furr@…]

I'd be happy to test any changes you make.

[gwright@…]

OK, I've fixed the 'traditional-cpp' typo.

As Mike mentioned, the bootstrap compiler depends on the readline-4 port. This is a dependency of the Jaguar build, so I don't quite understand what the problem is, unless Mike's build was against an out of date ports tree (or the -Pd options to cvs update were omitted).

The build error may be a preprocessor issue. It would be useful to know what gcc and Xcode versions are being used.

/gw

[gwright@…]

The ghc under Jaguar (10.2.x) issue has been resolved by removing Jaguar support from the portfile. There simply aren't enough people with machines still running Jaguar to track down these problems.

This was discussed on the list some time ago. The general consensus was that we would support the latest two OS versions.

Not the ideal solution but probably the best we can do.

/gw