Linker limit workaround on Darwin causes buildEnv environments to conflict

[jwiegley]

In commit 7131e06, a workaround was introduced to link all Haskell dylibs from a lib/links directory. However, this directory is installed into any environment that builds a Haskell executable, causing environments made with buildEnv to conflict in those files.

Since I have many such environments in my configuration, this change forces me to maintain a set of priorities. It would be better if the links directory was somehow made local to the buildEnv.

[jwiegley]

Note that using this throughout my configuration provides a workaround:

    (haskell.lib.justStaticExecutables haskellPackages.bench)

[henrytill]

I ran into the same problem, merely trying to upgrade my user environment which contained the following:

haskellPackages.ghc
haskellPackages.cabal-install
haskellPackages.cabal2nix

which results in:

building path(s) ‘/nix/store/cs1vaznndfaivhklhv6pbni9n0l41zmj-user-environment’
Wide character in die at /nix/store/64jc9gd2rkbgdb4yjx3nrgc91bpjj5ky-buildenv.pl line 79.
collision between ‘/nix/store/jl3nflpnn9lmnwk0ap6r0rfx9pr0m0hq-cabal2nix-2.2/lib/links/libHShashable-1.2.6.0-AQZDze8miOYLRSXNmI0CCc-ghc8.0.2.dylib’ and ‘/nix/store/4b2i5k6s2cllgzr2r6hfq00g0g93cj86-cabal-install-1.24.0.2/lib/links/libHShashable-1.2.6.0-AQZDze8miOYLRSXNmI0CCc-ghc8.0.2.dylib’; use ‘nix-env --set-flag priority NUMBER PKGNAME’ to change the priority of one of the conflicting packages

I too worked around the problem by overriding cabal2nix with (haskell.lib.justStaticExecutables haskellPackages.cabal2nix).

I can't help but wonder if there's some way that paths could be merged to avoid this problem.

Ref: #22810

[mmahut]

Any news on this issue?

[stale]

I marked this as stale due to inactivity. → More info