You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use these tools with an older MacOS system like 10.6.8, you will need to supplement the older MacOSX SDK with newer features using MacPorts and the macports-legacy-support library.
cabal will accept direction on adding extra include directories to the build, and also will accept additional linked in libraries. Linking in the legacy-support library statically seems most appropriate.
To add these to all cabal builds, edit the config file at:
~/.cabal/config
I modified these items (NB: indentation is important):
and after doing that, when building ghc software using cabal, legacy-support is used and linked in automatically.
This takes care of most (but not always all) SDK issues.
Of course you will need to have a reasonable ghc version on your PATH or ghc won't be found during the build. You also need to have the PATH to MacPorts newer toolchain parts available (usually /opt/local/bin).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
To use these tools with an older MacOS system like 10.6.8, you will need to supplement the older MacOSX SDK with newer features using MacPorts and the macports-legacy-support library.
cabal will accept direction on adding extra include directories to the build, and also will accept additional linked in libraries. Linking in the legacy-support library statically seems most appropriate.
To add these to all cabal builds, edit the config file at:
I modified these items (NB: indentation is important):
and after doing that, when building ghc software using cabal, legacy-support is used and linked in automatically.
This takes care of most (but not always all) SDK issues.
Of course you will need to have a reasonable ghc version on your PATH or ghc won't be found during the build. You also need to have the PATH to MacPorts newer toolchain parts available (usually
/opt/local/bin
).Beta Was this translation helpful? Give feedback.
All reactions