I suspect this is either a problem with ghc
or cabal-install
:
I used to get build information in such a format:
Resolving dependencies...
Configuring ltk-0.8.0.6...
Building ltk-0.8.0.6...
Preprocessing library ltk-0.8.0.6...
[ 1 of 12] Compiling Graphics.UI.Frame.Panes ( src/Graphics/UI/Frame/Panes.hs, dist/build/Graphics/UI/Frame/Panes.o )
[ 2 of 12] Compiling Graphics.UI.Editor.Parameters ( src/Graphics/UI/Editor/Parameters.hs, dist/build/Graphics/UI/Editor/Parameters.o )
[ 3 of 12] Compiling Control.Event ( src/Control/Event.hs, dist/build/Control/Event.o )
[ 4 of 12] Compiling MyMissing ( src/MyMissing.hs, dist/build/MyMissing.o )
[ 5 of 12] Compiling Graphics.UI.Editor.Basics ( src/Graphics/UI/Editor/Basics.hs, dist/build/Graphics/UI/Editor/Basics.o )
[ 6 of 12] Compiling Graphics.UI.Editor.MakeEditor ( src/Graphics/UI/Editor/MakeEditor.hs, dist/build/Graphics/UI/Editor/MakeEditor.o )
[ 7 of 12] Compiling Text.PrinterParser ( src/Text/PrinterParser.hs, dist/build/Text/PrinterParser.o )
However, now I get this type of build output:
Configuring binary-shared-0.8.3...
Configuring cairo-0.12.5.1...
Building binary-shared-0.8.3...
Building cairo-0.12.5.1...
Installed binary-shared-0.8.3
Configuring ghc-paths-0.1.0.9...
Building ghc-paths-0.1.0.9...
Installed ghc-paths-0.1.0.9
Configuring glib-0.12.5.0...
As you can see, cabal-install
or ghc
, whichever is causing the problem, seems to be inducing undesirable laconism now. According to my cabal config, I am running at a default verbosity level of 1. Is there some configuration option that could have caused this particular behavior? In other words, how can I restore the original behavior? Version 1.18.0.2
Thanks to @Michael Snoyman for pointing out that configuring a jobs
parameter or explicitly passing it as a -j
flag will redirect much of the information that pertains to build output to a text file. More information is available here.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With