Hard-coded /Developer path in Mac ghc

[Ahruman]

The Haskell Platform package for Mac OS X installs a /usr/bin/ghc script which hard-codes the path to gcc as:

pgmgcc="/Developer/usr/bin/gcc"

This is incorrect, as Xcode tools can be installed at semi-arbitrary locations, and there may be several versions installed. The correct approach is:

developerpath=`xcode-select --print-path` # Produces "/Developer" or alternative path
pgmgcc="$developerpath/usr/bin/gcc"

[altaic]

I believe this issue has been fixed; with Haskell Platform 2012.0.0 (OS X, 64 bit), my /usr/bin/ghc looks like the following (no references to /Developer, or even gcc, for that matter):

#!/bin/sh
exedir="/Library/Frameworks/GHC.framework/Versions/7.4.1-x86_64/usr/lib/ghc-7.4.1"
exeprog="ghc-stage2"
executablename="$exedir/$exeprog"
datadir="/Library/Frameworks/GHC.framework/Versions/7.4.1-x86_64/usr/share"
bindir="/Library/Frameworks/GHC.framework/Versions/7.4.1-x86_64/usr/bin"
topdir="/Library/Frameworks/GHC.framework/Versions/7.4.1-x86_64/usr/lib/ghc-7.4.1"
executablename="$exedir/ghc"
exec "$executablename" -B"$topdir" ${1+"$@"}

[altaic]

Oops, I meant to say: Haskell Platform 2012.2.0.0

[simonmar]

We still have a gcc path in the settings file, I believe.

[Ahruman]

There is indeed a fixed path in settings, but it doesn’t have the same problem of relying on an Xcode install path. Instead, GHC requires the command line developer tools package, now a separate installation which doesn’t have the option of a custom path.

(The approach of using xcode-select --print-path is still valid, and produces /Applications/Xcode.app/Contents/Developer by default under the new regime, but there’s no clear advantage to doing that any longer.)

[simonmar]

Ok, so you're saying that now gcc is always in /usr/bin and is independent of the XCode installation path, it doesn't matter that we have a fixed path in our settings file?

[Ahruman]

Yes. Or close enough to yes for rock’n’roll.