Open aspiwack opened 6 years ago
Reproduced it on my end with the latest from master.
Is there a workaround to this? Something like feeding all .hs
files manually to haddock?
I experienced a very similar issue with just stack haddock
(without --no-strip
option) since upgrading GHC into ver. 8.6.3 or ver. 8.6.4 (I tried with LTS-13.12 and LTS-13.11).
Should I file a separate issue?
My stack:
> stack --version
Version 1.9.1, Git revision f9d0042c141660e1d38f797e1d426be4a99b2a3c (6168 commits) x86_64 hpack-0.31.0
@igrep I think you should, or at least add the error message
For the records: I worked around this by adding --no-haddock-deps
to the invocation. The trade off is that the produced doc doesn't have links to, say, types in the dependencies.
General summary/comments
Passing
--no-strip
(or collectively--no-library-stripping --no-executable-stripping
) tostack haddock
orstack --profile
fails to compute build plan (pretty much as if no resolver was passed).It interferes with adding
to the
stack.yaml
.Steps to reproduce
$ stack new foo && cd foo
$ stack haddock --no-strip
(or$ stack build --profile --no-strip
)Expected
Success
Actual
Verbose output
Stack version
Method of installation
stack upgrade