Arch Linux User Repository

The problem appears to be that the library also built by this package libHSmatterhorn-... is not installed alongside the binary, so the binary cannot find it. Something like the following in the package step fixes this:

install -Dm0755 -t "$pkgdir/usr/lib/" $(find . -name "libHSmatterhorn-${pkgver}-*.so" -type f)

However, ldd /usr/bin/matterhorn shows that it links against quite a lot of libraries that are "installed" in the .cabal/store of the user who built it, which means that likely only the user building the package has sufficient permissions to actually execute the built binary.

@tdussa Did you build in a chroot? In that case the chroot might have had newer dependencies than your host system. The best way is to fully update your host, then rebuild this package.

I just ran into the same problem directly after building and installing matterhorn. If I understand correctly, then in this case any dependencies should be fine, correct? I have not updated anything at all after building and installing matterhorn, so no other Haskell-based package could have triggered a rebuild of any component.

So... What to do? How to fix this?

@zobi8225 You will need to rebuild this any time you update other haskell packages on your system.

Same problem :

matterhorn: error while loading shared libraries: libHSmatterhorn-50200.17.0-inplace-ghc9.0.2.so: cannot open shared object file: No such file or directory

I was already doing this.

I think I found the root cause though : I build aur packages in a clean chroot, and the PKGBUILD built haskell-dependencies that are in the official repositories (like xdg-basedir), Since ghc is not determinist, the official version was not the same than the one built during matterhorn build, hence the error.

I fixed this using arch-hs to generate another PKGBUILD, which correctly list dependencies and generate PKGBUILD for those not present in the arch repos. The downside is that you have to build those in order, but it works great.

@VannTen First, update your base system so that all Haskell packages are fresh (they get rebuilds often daily). Then actually rebuild this, not just reinstall it. Don't rely on makepkg or yay to do it for you, force it (e.g. with makepkg -Cf or yay --aur --rebuild -S matterharn).

I get matterhorn: error while loading shared libraries: libHSxdg-basedir-0.2.2-8ecb76da6be77d73b9461eff4f8ad8ead6925c6836da9fc507f05fc3db6963a5-ghc8.10.2.so: cannot open shared object file: No such file or directory when trying to launch matterhorn after building it in a clean chroot.

I thought it was a dependencies mismatch, so I tried to bump the version (latest is 50200.11.0) but I get another error : matterhorn: error while loading shared libraries: libHSmatterhorn-50200.11.0-inplace-ghc8.10.2.so: cannot open shared object file: No such file or directory Which seems like a internal lib. Do you see the same result, or is it my system ?

Hi, package is broken now?

Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: matterhorn-50200.8.0 (user goal)
[__1] next goal: brick (dependency of matterhorn)
[__1] rejecting: brick-0.54 (conflict: matterhorn => brick>=0.52.1 && <0.53)
[__1] skipping: brick-0.53 (has the same characteristics that caused the
previous version to fail: excluded by constraint '>=0.52.1 && <0.53' from
'matterhorn')
[__1] trying: brick-0.52.1
[__2] next goal: base (dependency of matterhorn)
[__2] rejecting: base-4.14.0.0/installed-4.14.0.0 (conflict: brick =>
base<=4.13.0.0)
[__2] skipping: base-4.14.0.0 (has the same characteristics that caused the
previous version to fail: excluded by constraint '<=4.13.0.0' from 'brick')
[__2] rejecting: base-4.13.0.0, base-4.12.0.0, base-4.11.1.0, base-4.11.0.0,
base-4.10.1.0, base-4.10.0.0, base-4.9.1.0, base-4.9.0.0, base-4.8.2.0,
base-4.8.1.0, base-4.8.0.0, base-4.7.0.2, base-4.7.0.1, base-4.7.0.0,
base-4.6.0.1, base-4.6.0.0, base-4.5.1.0, base-4.5.0.0, base-4.4.1.0,
base-4.4.0.0, base-4.3.1.0, base-4.3.0.0, base-4.2.0.2, base-4.2.0.1,
base-4.2.0.0, base-4.1.0.0, base-4.0.0.0, base-3.0.3.2, base-3.0.3.1
(constraint from non-upgradeable package requires installed instance)
[__2] fail (backjumping, conflict set: base, brick, matterhorn)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: brick, base, matterhorn

==> ERROR: A failure occurred in build().
    Aborting...