In order to work around that bug in regex-tdfa-text, you'll likely need to check out the package locally, or possibly via the Git packages feature. Adding ghc-options to stack.yaml (something we've been discussing) may help you get a reliable build out of this situation.
Alright, I've read the discussion here. I'm not sure I understand the definition of "wanted". Shouldn't regex-tdfa-text be a wanted dependency in my case?
I actually wanted to build Leksah with Stack, but I cannot do that in a straightforward way due to the regex-tdfa-text package. Problems like this are going to happen again and providing per-package GHC options in stack.yaml would provide an easy solution.
Thanks, setting ghc-options in the stack.yaml works.
--ghc-options still has no effect when building the regex package alone, though. I think how this works exactly needs to be documented somehow and the user should be informed. As a user you'd expect the options to apply at the very least to the packages you've specified to be built.
When calling for example
stack build regex-tdfa-text --ghc-options -XFlexibleContexts(a workaround for a bug in that package) the option --ghc-options has no effect and the build fails.
It's the same problem as in this thread
I've looked at the sources and the reason is this line. If I change it to
if Trueand rebuild Stack, the GHC Options are passed correctly.
There's obviously a reason why this check is there, but it doesn't work properly.
The text was updated successfully, but these errors were encountered: