Near as I can tell, it _is_ going to stderr just like you'd expect too $ stack build > log_output simple-library-0.1.0.0: unregistering (local file changes: src/Lib.hs) simple-library-0.1.0.0: build Preprocessing library simple-library-0.1.0.0... [1 of 1] Compiling Lib ( src/Lib.hs, .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Lib.o )
/home/callen/work/simple-library/src/Lib.hs:7:3: warning: [-Wunused-do-bind] A do-notation statement discarded a result of type ‘[Char]’ Suppress this warning by saying ‘_ <- return "hi"’ Preprocessing executable 'simple-library-exe' for simple-library-0.1.0.0... simple-library-0.1.0.0: copy/register Installing library in /home/callen/work/simple-library/.stack-work/install/x86_64-linux/lts-7.0/8.0.1/lib/x86_64-linux-ghc-8.0.1/simple-library-0.1.0.0-IZ2irAKiR4w8tX3NVir98W Installing executable(s) in /home/callen/work/simple-library/.stack-work/install/x86_64-linux/lts-7.0/8.0.1/bin Registering simple-library-0.1.0.0... [ callen@pardalis ~/work/simple-library master ✗ ] $ stack build 2>&1 > log_output On Wed, Sep 14, 2016 at 2:21 PM, Christopher Allen <c...@bitemyapp.com> wrote: > What are you talking about? > > $ stack build > simple-library-0.1.0.0: unregistering (local file changes: src/Lib.hs) > simple-library-0.1.0.0: build > Preprocessing library simple-library-0.1.0.0... > [1 of 1] Compiling Lib ( src/Lib.hs, > .stack-work/dist/x86_64-linux/Cabal-1.24.0.0/build/Lib.o ) > > /home/callen/work/simple-library/src/Lib.hs:7:3: warning: [-Wunused-do-bind] > A do-notation statement discarded a result of type ‘[Char]’ > Suppress this warning by saying ‘_ <- return "woot"’ > Preprocessing executable 'simple-library-exe' for simple-library-0.1.0.0... > > On Wed, Sep 14, 2016 at 2:10 PM, Patrick Pelletier > <ppell...@funwithsoftware.org> wrote: >> On 9/14/16 10:47 AM, David Feuer wrote: >>> >>> >>> While we're griping about stack: it seems to place compiler output from >>> -ddump-... in mysterious places that are hard to find without Google, and >>> (worse) it seems to do something with stack test output that even Google >>> can't discover. >>> >> >> Also, compiler warnings get squirreled away in a file that I have to go >> hunting for. It would be nice to have an option to print warnings (for >> local packages, not dependencies) to stderr. >> >> --Patrick >> >> >> _______________________________________________ >> Haskell-community mailing list >> Haskell-community@haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community > > > > -- > Chris Allen > Currently working on http://haskellbook.com -- Chris Allen Currently working on http://haskellbook.com _______________________________________________ Haskell-community mailing list Haskell-community@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community