i would make sure you're using the ghc version you *think*  you're using

i've never had that problem with a self managed style install (which should be equiv to using ghcup's setup). i'm at 8.10.7 at the moment.

whats the output of `which -a ghc`  and `which ghc`?

mixing several ghc installs of the same version can be a problem.  ghcup should just match the official builds generally


On Mon, Oct 11, 2021 at 9:55 PM Steven Smith <steve.t.smith@gmail.com> wrote:
I’m a maintainer of the MacPorts ghc port. The MacPorts installations do not have this issue, whether installed from the buildbot binaries or compiled from source, that all work on multiple macOS versions 10.9–11.  Here’s the build recipe: https://github.com/macports/macports-ports/blob/master/lang/ghc/Portfile

The iconv symbol issue is known, https://gitlab.haskell.org/ghc/ghc/-/issues/18752, and packages like MacPorts must build around it.

This looks like something specific to your configuration.

If you believe that there is an issue outside your system, please initiate a trac ticket at https://trac.macports.org.


On Oct 11, 2021, at 5:00 AM, David Duke <duke.j.david@gmail.com> wrote:

I have a conundrum on which advice would be appreciate. Does
anyone know how to successfully install ghc on OSX 
I've tried various binary instalation routes:
macports, brew, direct binary downloads from haskel.org

_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users