> On Mon, Apr 09, 2001 at 06:44:20PM -0400, Ivan Jager wrote:
> > What about:
> > make [make options] 2>&1 | tee output.log
>
>I prefer not to have to sort through to find the warnings
> and errors. Your approach has the benefit of context, mine of
> "purity" of information (
> On Mon, Apr 09, 2001 at 02:18:03PM -0700, Linux User wrote:
> > Hello everyone,
> > When compiling a C\C++ program is it possible to output any warning
> > during the compile to a file, so they can be reviewed later?
>
> gcc [options string] > stdout.log 2> stderr.log, or
>
> make [make optio
Thanks Chris.
That's exactly what I wanted. Outputing just the warnings into their own
file makes it quicker then having to scan the entire output.
Thanks,
Jim H
Chris Petro wrote:
>
> On Mon, Apr 09, 2001 at 02:18:03PM -0700, Linux User wrote:
> > Hello everyone,
> > When compiling a
On Mon, Apr 09, 2001 at 06:44:20PM -0400, Ivan Jager wrote:
> What about:
> make [make options] 2>&1 | tee output.log
I prefer not to have to sort through to find the warnings
and errors. Your approach has the benefit of context, mine of
"purity" of information (for want
What about:
make [make options] 2>&1 | tee output.log
Chris Petro wrote:
>
> On Mon, Apr 09, 2001 at 02:18:03PM -0700, Linux User wrote:
> > Hello everyone,
> > When compiling a C\C++ program is it possible to output any warning
> > during the compile to a file, so they can be reviewed later?
On Mon, Apr 09, 2001 at 02:18:03PM -0700, Linux User wrote:
> Hello everyone,
> When compiling a C\C++ program is it possible to output any warning
> during the compile to a file, so they can be reviewed later?
gcc [options string] > stdout.log 2> stderr.log, or
make [make options] > stdout.log
Hello everyone,
When compiling a C\C++ program is it possible to output any warning
during the compile to a file, so they can be reviewed later?
Thanks,
Jim H
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/m
