Skip to content
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

cabal haddock --haddock-for-hackage --enable-doc failed with ghc-9.2.4 #8553

Open
Lev135 opened this issue Oct 24, 2022 · 3 comments
Open

cabal haddock --haddock-for-hackage --enable-doc failed with ghc-9.2.4 #8553

Lev135 opened this issue Oct 24, 2022 · 3 comments

Comments

@Lev135
Copy link

Lev135 commented Oct 24, 2022

Describe the bug
While building documenation for hackage for the project with case-insensitive in build-depends I've got the following error:

haddock: internal error: C:\Cabal\store\ghc-9.2.4\case-insensit_-1.2.1.0-c5e15b8a1dff4c5e3677e9ed014cacac260e8dc1\share\doc\html\doc-index.json: openBinaryFile: does not exist (No such file or directory)

To Reproduce

  • init a cabal project with library
  • remove base version bounds
  • add case-insensitive to build-depends
  • run cabal haddock --haddock-for-hackage --enable-doc --with-compiler=ghc-9.2.4

It works fine if you disable one of the options --haddock-for-hackage or --enable-doc or change ghc version to ghc-8.10.7 or if I exclude case-insensitive from dependencies

Expected behavior
Documentation should be successfully build, as for ghc-8.10.7

System information

  • Operating system: Windows 10
  • cabal-install version 3.6.2.0
  • ghc-version: ghc-9.2.4
@ulysses4ever
Copy link
Collaborator

ulysses4ever commented Oct 24, 2022

This is a haddock bug, not cabal bug, I think. And I seem to remember that it's known but would need to search their tracker...

@jneira
Copy link
Member

jneira commented Oct 24, 2022

I would bet it is something related with the infamous long paths limit in windows, the rest of packages might have shorter names
Moving store-dir to a really shorter path (C:\cs f.e.) could help if that is the case

@jasagredo
Copy link
Collaborator

This is not our bug. Should we close it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants