3 ms·
To make this discussion more concrete, here are some problems I've thus far found on the Mac: - GHC ships with the wrong compiler path for (some version s of?)
by jarrett 12y ago
To make this discussion more concrete, here are some problems I've thus far found on the Mac:
- GHC ships with the wrong compiler path for (some version s of?) OS X, causing various C-related stuff to fail. https://gist.github.com/cartazio/7131371 https://gist.github.com/cartazio/7131371
- ghc-pkg gets itself into an error state pretty quickly after installing a fresh Haskell Platform, and ghc-pkg recache must be run.
- You must manually request the latest version of cabal-install. cabal install cabal-install by default gives you a version without sandboxes.
These are just a few of the issues that come to mind; I've run into quite a few more in my Haskell explorations. You can imagine how this state of affairs would cause a lot of developers to give up. I'm not at all blaming anyone in the truly wonderful Haskell community. Everything about Haskell is done volunteers, and I'm grateful for their work. I'm just offering a theory as to why Haskell hasn't been embraced as warmly as, say, Node or Go.
- dllthomas 12y ago"- You must manually request the latest version of cabal-install. cabal install cabal-install by default gives you a version without sandboxes." So far as I'm aware, doing a cabal update cabal install cabal-install should always get you the latest version of cabal-install. One thing people encounter frequently, that may be confused for this, is that cabal doesn't install things system-wide, and so you have to 1) make sure that the place cabal is installing things is in your path, and 2) possibly make sure your shell hasn't cashed the location of the old system-wide version of cabal. It's totally possible that there's a bug that's more specifically as you describe that I just haven't heard of, of course - just trying to help if I'm able.