[Haskell-cafe] Upgrading ByteString causes (seemingly) impossible RTS linker errs

Don Stewart dons at galois.com
Sun Jan 27 15:24:46 EST 2008

> Recently I've been developing my IRC bot a little further, and in the
> midst of it I have come across a very problematic issue that revolves
> around GHC-dependencies vs. application-dependencies. The central issue
> is ByteString.
> Currently, the ghc package depends on bytestring- However, the
> current version of ByteString I have installed is To keep
> compatability with bytestring-dependent libraries that were built
> against, you have to recompile of all these libs against
> For example, I had to build a newer version of zlib against
>, because the older version was built for, which mean
> that it was not possible to build cabal-install because of the
> incompatabilities (it needed bytestring and zlib.)
> The problem is that if you have a package that depends on ghc as a
> library, but also depends on bytestring > or any library built
> against it, you'll get pretty much unstoppable linker errs, since all the
> symbol names in the ghc package are hardwired for (meaning you
> can't do 'ghc-pkg update' for it) forcing it to be loaded.

It should be possible to specify that your lib depends on exactly in the .cabal file.

-- Don

More information about the Haskell-Cafe mailing list