Re: Avoid redirecting to /dev/null

[Noah Misch]

On Fri, Feb 04, 2005 at 04:40:23PM +0530, Annamalai Gurusami wrote:
> Hi.
> 
> 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?

Libtool creates this behavior.  Please direct further queries to a Libtool list.

> 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

Libtool builds each file twice, once PIC and once non-PIC.  Since the warnings
and errors probably do not differ between those passes, it suppresses output for
the second run.