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 new-haddock fails for build-type:configure #5503

Closed
hvr opened this issue Aug 6, 2018 · 2 comments · Fixed by #5573
Closed

cabal new-haddock fails for build-type:configure #5503

hvr opened this issue Aug 6, 2018 · 2 comments · Fixed by #5573

Comments

@hvr
Copy link
Member

hvr commented Aug 6, 2018

Reproduction:

$ cabal get network-2.7.0.2 && cd network-2.7.0.2/
$ cabal new-haddock -w ghc-8.4.3 -v
$ cabal new-haddock -w ghc-8.4.3 
Build profile: -w ghc-8.4.3 -O1
In order, the following will be built (use -v for more details):
 - network-2.7.0.2 (first run)
cabal: Unrecognised flags: lib:network
Warning: Failed to build documentation for network-2.7.0.2.

using -v reveals:

...
configure: creating ./config.status
config.status: creating network.buildinfo
config.status: creating include/HsNetworkConfig.h
configure: WARNING: unrecognized options: --with-compiler
Reading parameters from
/tmp/network-2.7.0.2/dist-newstyle/build/x86_64-linux/ghc-8.4.3/network-2.7.0.2/build/network.buildinfo
whenReRegister: nothing to register
Using self-exec internal setup method with build-type Configure and args:
["act-as-setup","--build-type=Configure","--","haddock","--verbose=2","--builddir=/tmp/network-2.7.0.2/dist-newstyle/build/x86_64-linux/ghc-8.4.3/network-2.7.0.2","lib:network"]
/stuff/dot-cabal/bin/cabal act-as-setup --build-type=Configure -- haddock
--verbose=2
--builddir=/tmp/network-2.7.0.2/dist-newstyle/build/x86_64-linux/ghc-8.4.3/network-2.7.0.2
lib:network
cabal: Unrecognised flags: lib:network
Warning: Failed to build documentation for network-2.7.0.2-inplace.
@hvr
Copy link
Member Author

hvr commented Aug 6, 2018

This is related to #5261 which fixed the same symptom for build-type: Custom; however, the issue at hand is about build-type: Configure!

@hvr
Copy link
Member Author

hvr commented Aug 6, 2018

@alexbiehl suggests the culprit to be

missing the logic from

hvr added a commit to hvr/cabal that referenced this issue Sep 8, 2018
…nfigure`

In the course of 4466310 (see haskell#5526) the
`Setup.hs haddock` CLI was extended to allow component ids to be passed
as positional arguments. However, `autoconfUserHooks` which is used in
case of `build-type: Configure` wasn't updated accordingly, and consequently
this caused `new-haddock` to break for packages using `Configure`.

Fixes haskell#5503
hvr added a commit to hvr/cabal that referenced this issue Sep 8, 2018
…nfigure`

In the course of 4466310 (see haskell#5526) the
`Setup.hs haddock` CLI was extended to allow component ids to be passed
as positional arguments. However, `autoconfUserHooks` which is used in
case of `build-type: Configure` wasn't updated accordingly, and consequently
this caused `new-haddock` to break for packages using `Configure`.

cc @alexbiehl

Fixes haskell#5503
hvr added a commit that referenced this issue Sep 8, 2018
…nfigure`

In the course of 4466310 (see #5526) the
`Setup.hs haddock` CLI was extended to allow component ids to be passed
as positional arguments. However, `autoconfUserHooks` which is used in
case of `build-type: Configure` wasn't updated accordingly, and consequently
this caused `new-haddock` to break for packages using `Configure`.

cc @alexbiehl

Fixes #5503

(cherry picked from commit 86dabda)
hvr added a commit that referenced this issue Sep 8, 2018
@hvr hvr closed this as completed in #5573 Sep 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment