Alp Mestanogullari
Alp Mestanogullari
Not sure about what you need to know to get things to work in your setup, but we could slightly tweak ghc.nix so that it gives us the current environment...
I don't think `ghc.nix` comes with hoogle. You could try adding that, and whatever else is necessary, to your `buildInputs`. Note that you probably don't need a separate nix derivation...
I'm just running `nix-shell` manually to enter the environment in my terminal, and this works smoothly, so I suspect this is more a direnv/nix-direnv/emacs-direnv question than a ghc.nix one, isn'...
Well, at the moment `ghc.nix` doesn't even try to support it (by supplying suitable definitions for the various relevant phases of building a derivation: `configurePhase`, `buildPhase`, etc). We've just all...
GHC CI, you mean? I have written the somewhat hacky and poorly named `ghc-repro` tool to generate docker and build scripts to reproduce a given CI job against a given...
Any chance you could figure out what derivation you need to have in scope for `nm` to be available? We could add it to the env when on darwin.
Would it be that bad for other systems if the test was changed to just invoke `ls` assuming it's in the PATH? I'd expect this to work on most systems...
Put together a PR for those `process` tests at https://github.com/haskell/process/pull/133
What's the current status on this, @Mistuke ? Do we have the necessary pieces to support generating `.dll`s on Windows?
No worries, I just wanted to know whether we had everything needed for me to tackle the hadrian side or not. Just ping us when it's all there :-)