-
Notifications
You must be signed in to change notification settings - Fork 689
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-build doesn't produce logs for local packages #5901
Comments
Was If anything, I'd expect Grepping for cabal/cabal-install/src/Distribution/Client/Setup.hs Lines 1889 to 1891 in 8248c3d
So, the CLI flag triggers an InstallFlag called installLogFile . It was commited 14 years back here: 5702472 and was supposed for cabal install . And today it's essentially used only in Distribution/Client/Install.hs . No wonder, it has no impact on v2-build .
Arguably, the bug here is that |
Could you tell me what are my options for getting verbose build log from Cabal (building local packages)? |
@mouse07410 the only workaround I’m aware about is to redirect |
Well, it's not a beautiful workaround - but it works. |
This should be easy to fix. All the changes should be contained in |
Some good related work is here, I think: @gbaz revived |
Thanks @ulysses4ever I was going to suggest we close this and #6811 as duplicates of #8456 but I had missed the ticket you mention. ninja edit: I am tempted to suggest we could simply log all local package builds in the dist folder (even by default) but I cannot have a clear picture until we collect all these tickets into a single one. ninja edit 2: #7567 is mostly around build reports and only incidentally mentions build-log. I agree we should not remove it altogether. |
FWIW, after #9524, this can be very easily seen in
We /never/ use a log file for building inplace packages, so regardless of the default log file or specified via cli flags, we will write the output of an inplace build to the stdout (see setup in the same file, which calls withLogging ).
|
As far as I can tell
cabal new-build
no longer produces log files for local package builds. For instance,Moreover,
-v2
shows no indication that a log was generated. I have a vague sense that this used to work so I suspect there is a regression here.The text was updated successfully, but these errors were encountered: