-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*** abort because of serious configure-time warning from Cabal #134
Comments
In this particular case it's overriding Cabal package with GHC core package Cabal. |
yea, nulling works! Just wanted to make sure if there is a better way. So in general all core packages should be nulled? Could this be done automatically by stack2nix for a specific compiler version? Thanks for your help! |
This is taken care in https://github.com/input-output-hk/stack2nix/blob/master/src/Stack2nix/Render.hs#L41 To handle this properly, it should be dynamic based on GHC version given, which is what #84 is for. |
I'm having this issue trying to install stack2nix itself on macOS 10.14 via log of error:
|
For now best to use it from NixOS 18.09, I'll fix nixpkgs master. |
I also just hit this when using |
Note: waiting on #84 |
- Now fetching nixpgks with fetchFromGitHub by computing and saving the sha256 at update time - Detecting core GHC libraries and setting them to null to fix builds, workaround for input-output-hk/stack2nix#134 - Add override directory to fix builds for specific ghc versions - Speed up builds by disabling library profiling for everything - New nix file structure with powerful selection mechanisms
probably I am doing something wrong. I often get this error when building with the
default.nix
that was generated bystack2nix
:for example in one case:
Usually the version is the same. I had the same warning with a bunch of other packes, e.g. mtl, text, parsec, stm, which I managed to fix by adding:
I would like to understand why this happens and how it can be best avoided. Unfortunately I can't share my whole package to reproduce this. Do you have any idea what this is all about?
The text was updated successfully, but these errors were encountered: