Re: Avoid redirecting to /dev/null

[Ralf Wildenhues]

* Annamalai Gurusami wrote on Fri, Feb 04, 2005 at 12:10:23PM CET:
> 
> We are using autoconf tools for our project.  After doing ./configure
> when I issue the make command, the compiler output is being redirected
> to /dev/null.  How to avoid this redirection?
> 
*snip*
> 
> if /bin/sh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. 
> -I ../base/  -g   -MT Telnet.lo -MD -MP -MF ".deps/Telnet.Tpo" -c -o 
> Telnet.lo Telnet.cc; \
> then mv -f ".deps/Telnet.Tpo" ".deps/Telnet.Plo"; else rm -f 
> ".deps/Telnet.Tpo"; exit 1; fi
> mkdir .libs
>  g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I ../base/ -g -MT Telnet.lo -MD -MP -MF 
> .deps/Telnet.Tpo -c Telnet.cc  -fPIC -DPIC -o .libs/Telnet.o
>  g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I ../base/ -g -MT Telnet.lo -MD -MP -MF 
> .deps/Telnet.Tpo -c Telnet.cc -o Telnet.o >/dev/null 2>&1
*snip*
> 
> I see that not all the command output is redirected.  Only some of
> them are redirected.  I just don't want to miss any warnings or errors
> from the compiler.  Any thoughts on this much appreciated.  Thanks.

The redirection is done by libtool.  Its done because each file is
compiled twice, once position-independent (PIC) for use in shared
libraries, and once position dependent.  Since most of the time the
warnings for both compilations would be identical, it is seen as
useful to see the output only once.

You can avoid the redirection with the
 -no-suppress
libtool option.  More info can be found in the Libtool info pages.

Regards,
Ralf