It might even be a good idea to send this patch to Dyre upstream. I doubt they really want to use GHC path stored during compilation for _dynamic_ reconfiguration.
On Mon Feb 23 2015 at 0:18:58 Kirill Elagin <kirela...@gmail.com> wrote: > Well, the author of the issue I pointed out is correct in saying that they > use Dyre which in turn uses ghc-paths. I checked ghc-paths and I believe > what they do is store the path to GHC _they were compiled with_. > > So errr... Looks like we are stuck in a loop. I guess your best bet is to > patch Dyre not to use ghc-paths. > > On Mon Feb 23 2015 at 23:59:51 Arseniy Seroka <ars.ser...@gmail.com> > wrote: > >> >> 2015-02-23 22:55 GMT+03:00 Kirill Elagin <kirela...@gmail.com>: >> >>> Does XMonad work in your case? >>> Can you import `System.Taffybar` in `ghci`? >>> >> >> Yes, xmonad works and I can import `System.Taffybar` in ghci. >> >> >> Might it be that, unlike XMonad, they do something more complicated to >>> invoke GHC? I didn’t check the source, but looks like they do. >>> Are you running this on a non-NixOS distro? In that case, the issue >>> <https://github.com/simonmar/ghc-paths/issues/4> probably explains >>> what’s going >>> >> >> I'm using Nixos. >> That's what they are doing. [1] >> >> [1] https://github.com/travitch/taffybar/blob/master/src/System/ >> Taffybar.hs#L204 >> >> >> -- >> Sincerely, >> Arseniy Seroka >> >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev