matterhorn @50200.15.0_1: Error: cabal: Ambiguous target 'matterhorn'

[cooljeanius (Eric Gallager)]

Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/matterhorn-50200.15.0" && /opt/local/bin/cabal --config-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/.home/.cabal/config build matterhorn -j16 --builddir=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/dist --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/destroot/opt/local --enable-relocatable 
DEBUG: system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/matterhorn-50200.15.0" && /opt/local/bin/cabal --config-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/.home/.cabal/config build matterhorn -j16 --builddir=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/dist --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/destroot/opt/local --enable-relocatable 
Error: cabal: Ambiguous target 'matterhorn'. It could be:
exe:matterhorn (component)
lib:matterhorn (component)


Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/matterhorn-50200.15.0" && /opt/local/bin/cabal --config-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/.home/.cabal/config build matterhorn -j16 --builddir=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/dist --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_matterhorn/matterhorn/work/destroot/opt/local --enable-relocatable 
Exit code: 1
Error: Failed to build matterhorn: command execution failed
DEBUG: Error code: CHILDSTATUS 97282 1
DEBUG: Backtrace: command execution failed

I'm on Big Sur with Xcode 13.

[cooljeanius (Eric Gallager)]

main.log for matterhorn

[cardi (calvin ardi)]

Thanks for the ticket---in summary, Matterhorn is currently not compileable with GHC 9.4.x (which is what MacPorts has) until upstream updates the client and API to use GHC 9.4.x.

Updating matterhorn to the latest version has been a long work-in-progress.

My understanding is that Matterhorn along with the ​mattermost-api depends on and is built using GHC 8.x and has not been tested with GHC 9.x. Because Matterhorn and the mattermost-api specify strict versions of dependencies, I've found that bumping version numbers isn't straightforward as I'm constantly running into conflicts (e.g., a dependency at some version is compatible with GHC 9 but not 8, etc).

That said, it does look like upstream is moving to GHC 9.4.x, so MacPorts can hopefully leverage those changes soon.

Unfortunately it looks like building the current version of Matterhorn (50200.15.0) with GHC 9.4.x will be broken until then.

[cardi (calvin ardi)]

Quick update: I've been tracking some of the upstream changes to matterhorn and mattermost-api, and it looks like there is active development to getting both of them working with GHC 9.4.x. I don't have a sense of the timeline for when the next release will be---I anticipate that the next release will build on MacPorts without any issues.

FWIW, I have tried recently to patch the matterhorn Cabal files to use updated dependencies, but there are some backwards incompatibilities with some dependencies that require code refactoring (that are already in place upstream).