Skip to content

ghc-asm has a poor shebang

During a cabal install of Snap and its dependency bytestring-mmap, ghc-asm complained that it couldn't run.

$ cabal install bytestring-mmap-0.2.1
Resolving dependencies...
Configuring bytestring-mmap-0.2.1...
Preprocessing library bytestring-mmap-0.2.1...
Building bytestring-mmap-0.2.1...
[1 of 3] Compiling System.IO.Posix.MMap.Internal ( System/IO/Posix/MMap/Internal.hs, dist/build/System/IO/Posix/MMap/Internal.o )
ghc: could not execute: /Library/Frameworks/GHC.framework/Versions/612/usr/lib/ghc-6.12.3/ghc-asm
cabal: Error: some packages failed to install:
bytestring-mmap-0.2.1 failed during the building phase. The exception was:
ExitFailure 1

Upon further investigation, it was determined that ghc-asm wouldn't run due to its shebang.

$ less /Library/Frameworks/GHC.framework/Versions/612/usr/lib/ghc-6.12.3/ghc-asm

#!/opt/local/bin/perl
$TARGETPLATFORM  = "i386-apple-darwin";

I installed !MacPorts in ~/macports, not /opt/local. When GHC was installed, it should have used the shebang

{{{ #!/usr/bin/env perl }}}

which does not depend on !MacPorts being installed in /opt/local, or for that matter !MacPorts being installed at all.

Specs:

  • GHC 6.12.3
  • Haskell Platform 2010.2.0.0
  • Mac OS X 10.6.6
  • !MacBook Pro 5,1
Trac metadata
Trac field Value
Version 6.12.3
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information