public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Output errors to stdout instead of stderr??
@ 1999-11-18 18:40 Paul Joseph Pearcy
  1999-11-18 23:30 ` Dirk Heinrichs
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Paul Joseph Pearcy @ 1999-11-18 18:40 UTC (permalink / raw)
  To: help-gcc

Is there anyway to output errors via stdout instead of the default
stderr???

Thanks,
Paul
loaded@purdue.edu

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-18 18:40 Output errors to stdout instead of stderr?? Paul Joseph Pearcy
@ 1999-11-18 23:30 ` Dirk Heinrichs
  1999-11-30 23:28   ` Dirk Heinrichs
  1999-11-19 10:17 ` Pat Ford
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 8+ messages in thread
From: Dirk Heinrichs @ 1999-11-18 23:30 UTC (permalink / raw)
  To: help-gcc

Paul Joseph Pearcy wrote:
> 
> Is there anyway to output errors via stdout instead of the default
> stderr???
In bash, extend your command by putting "2>&1" (without ") at the end.

Bye...

	Dirk

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-18 18:40 Output errors to stdout instead of stderr?? Paul Joseph Pearcy
  1999-11-18 23:30 ` Dirk Heinrichs
@ 1999-11-19 10:17 ` Pat Ford
  1999-11-30 23:28   ` Pat Ford
  1999-11-25  3:37 ` Ermanno Scaglione
  1999-11-30 23:28 ` Paul Joseph Pearcy
  3 siblings, 1 reply; 8+ messages in thread
From: Pat Ford @ 1999-11-19 10:17 UTC (permalink / raw)
  To: help-gcc

command 2>&1

ie make 2>&1

Previously, Paul Joseph Pearcy wrote in gnu.gcc.help:
{ Is there anyway to output errors via stdout instead of the default
{ stderr???
{ 
{ Thanks,
{ Paul
{ loaded@purdue.edu
{ 

--
Pat Ford                           email: pford@qnx.com
QNX Software Systems, Ltd.           WWW: http://www.qnx.com
(613) 591-0931      (voice)         mail: 175 Terence Matthews          
(613) 591-3579      (fax)                 Kanata, Ontario, Canada K2M 1W8

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-18 18:40 Output errors to stdout instead of stderr?? Paul Joseph Pearcy
  1999-11-18 23:30 ` Dirk Heinrichs
  1999-11-19 10:17 ` Pat Ford
@ 1999-11-25  3:37 ` Ermanno Scaglione
  1999-11-30 23:28   ` Ermanno Scaglione
  1999-11-30 23:28 ` Paul Joseph Pearcy
  3 siblings, 1 reply; 8+ messages in thread
From: Ermanno Scaglione @ 1999-11-25  3:37 UTC (permalink / raw)
  To: help-gcc

make 2>&1 under ksh/bash
make >& under csh

Paul Joseph Pearcy wrote:

> Is there anyway to output errors via stdout instead of the default
> stderr???
>
> Thanks,
> Paul
> loaded@purdue.edu

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Output errors to stdout instead of stderr??
  1999-11-18 18:40 Output errors to stdout instead of stderr?? Paul Joseph Pearcy
                   ` (2 preceding siblings ...)
  1999-11-25  3:37 ` Ermanno Scaglione
@ 1999-11-30 23:28 ` Paul Joseph Pearcy
  3 siblings, 0 replies; 8+ messages in thread
From: Paul Joseph Pearcy @ 1999-11-30 23:28 UTC (permalink / raw)
  To: help-gcc

Is there anyway to output errors via stdout instead of the default
stderr???

Thanks,
Paul
loaded@purdue.edu

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-19 10:17 ` Pat Ford
@ 1999-11-30 23:28   ` Pat Ford
  0 siblings, 0 replies; 8+ messages in thread
From: Pat Ford @ 1999-11-30 23:28 UTC (permalink / raw)
  To: help-gcc

command 2>&1

ie make 2>&1

Previously, Paul Joseph Pearcy wrote in gnu.gcc.help:
{ Is there anyway to output errors via stdout instead of the default
{ stderr???
{ 
{ Thanks,
{ Paul
{ loaded@purdue.edu
{ 

--
Pat Ford                           email: pford@qnx.com
QNX Software Systems, Ltd.           WWW: http://www.qnx.com
(613) 591-0931      (voice)         mail: 175 Terence Matthews          
(613) 591-3579      (fax)                 Kanata, Ontario, Canada K2M 1W8

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-18 23:30 ` Dirk Heinrichs
@ 1999-11-30 23:28   ` Dirk Heinrichs
  0 siblings, 0 replies; 8+ messages in thread
From: Dirk Heinrichs @ 1999-11-30 23:28 UTC (permalink / raw)
  To: help-gcc

Paul Joseph Pearcy wrote:
> 
> Is there anyway to output errors via stdout instead of the default
> stderr???
In bash, extend your command by putting "2>&1" (without ") at the end.

Bye...

	Dirk

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Output errors to stdout instead of stderr??
  1999-11-25  3:37 ` Ermanno Scaglione
@ 1999-11-30 23:28   ` Ermanno Scaglione
  0 siblings, 0 replies; 8+ messages in thread
From: Ermanno Scaglione @ 1999-11-30 23:28 UTC (permalink / raw)
  To: help-gcc

make 2>&1 under ksh/bash
make >& under csh

Paul Joseph Pearcy wrote:

> Is there anyway to output errors via stdout instead of the default
> stderr???
>
> Thanks,
> Paul
> loaded@purdue.edu

^ permalink raw reply	[flat|nested] 8+ messages in thread
end of thread, other threads:[~1999-11-30 23:28 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-11-18 18:40 Output errors to stdout instead of stderr?? Paul Joseph Pearcy
1999-11-18 23:30 ` Dirk Heinrichs
1999-11-30 23:28   ` Dirk Heinrichs
1999-11-19 10:17 ` Pat Ford
1999-11-30 23:28   ` Pat Ford
1999-11-25  3:37 ` Ermanno Scaglione
1999-11-30 23:28   ` Ermanno Scaglione
1999-11-30 23:28 ` Paul Joseph Pearcy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).