GHC-Options flags being ignored in newer Stack builds #2289
Milestone
Comments
|
Edit: I have reproduced this, it took some time (and an intervening episode of a popular television series), but using Stack 1.0.4.3 and the config.yaml I showed above, I am able to compile and run ghc-mod against my source. |
AaronFriel
changed the title
|
To check if |
|
I have bisected the issue to this commit causing the problem: c891a24 The commit prior, 6f108a1, works and I am able to build and run ghc-mod with it on Arch. I will see about getting you verbose output, but I can guarantee you that commit is causing the |
I had ghc-options lines in my |
AaronFriel
added a commit
to AaronFriel/stack
that referenced
this issue
Jun 25, 2016
Commit c891a24 created a regression, ghc-options were no longer applied to packages in the snapshot. The "mini build plan" for missing snapshot packages did not check the configuration's "ghc-options" settings at all, so even configurations with "apply-ghc-options: everything" would not apply those options. This commit, combined with a change to config.yaml, fixes these issues: DanielG/ghc-mod#762 IHaskell/IHaskell#636 To fix those issues, (usually located in ) should contain: And for snapshots already installed, the following command will force stack to rebuild them with those options: *Not tested:* Alternatively, add the line to . This may cause undesirable behavior in forcing all ghc-options changes to rebuild the snapshot.
mgsloan
added a commit
that referenced
this issue
Jun 30, 2016
Fix issue #2289, apply ghc-options to snapshot pkg
|
Fixed via #2305. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Arch Linux and other rolling distro users are experiencing errors due to the assembler using an unhandled relocation type.
See:
DanielG/ghc-mod#762
IHaskell/IHaskell#636
One trend with these reports is that some users report success from putting in their
config.yamlorstack.yamlthe lines:Or variations thereof (e.g.:
"*": ...).I'm experiencing this as well, even when I try to ghc-options all the things:
Even when I do that,
stack build cipher-aeswon't rebuild unless I use ghc-pkg to remove it (what?!) and even when I do, I still get these errors when using ghc-mod:An interesting observation is that some users report that the ghc-options command worked for them, specifically, @Shimuuar noted:
Since it looks like a GHC version that fixes this won't be released soon, I'm wondering if it might be possible to see why Stack 1.1.2 is not working with these options?
The text was updated successfully, but these errors were encountered: