This is the mail archive of the
mailing list for the GCC project.
Re: Piping output of compilation to /dev/null?
Christian Jönsson <firstname.lastname@example.org> writes:
> On Sun, May 12, 2002 at 09:31:42PM +0200, Christian Jönsson wrote:
>> When building GCC, I notice that in a few places the compiler output is
>> piped to /dev/null. I assume this is because we do not want to pollute
>> the log files with noise such as warnings...
> I should have said the compiler's stdout and stderr output...
Would this by any chance be places where libtool is being used to build
static and shared libraries?
libtool, when building the same file twice with different PIC options,
redirects stdout and stderr to /dev/null for the second build, under the
assumption that the compiler warning output the second time will be
identical to the first and there's no reason to repeat it.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>