Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?
Scott
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.
The account for depositing bribes is … ;v)
J. Scott Franko <jsfranko@switch.com> wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
“J. Scott Franko” wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
how 'bout using tee ? check into “use tee” …
-Th
well, there is already /usr/bin/tee 
Also, one could try porting
“script” from your favourite *BSD machine, it probably compiles right
out of the box…
-Th
No bribes for you
Colin Burgess wrote:
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.The account for depositing bribes is … ;v)
J. Scott Franko <> jsfranko@switch.com> > wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
Thanks! It would be cool to have that feature back. Bribe is being deposited
into swiss bank account #…
;o)
Scott
Colin Burgess wrote:
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.The account for depositing bribes is … ;v)
J. Scott Franko <> jsfranko@switch.com> > wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
I cannot get tqcc to re-direct. It seems the warning and error messages are
sent to stderr.
John
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:8sfqc4$iqj$2@nntp.qnx.com…
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.The account for depositing bribes is … ;v)
J. Scott Franko <> jsfranko@switch.com> > wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
\
Did you use the file descripters in you redirector to redirect both 1 and 2
(stdin and stdout) to a file?
John Love wrote:
I cannot get tqcc to re-direct. It seems the warning and error messages are
sent to stderr.John
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:8sfqc4$iqj$> 2@nntp.qnx.com> …
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.The account for depositing bribes is … ;v)
J. Scott Franko <> jsfranko@switch.com> > wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
\
John Love <John@tolltex.com> wrote:
I cannot get tqcc to re-direct. It seems the warning and error messages are
sent to stderr.
Use something like
qcc -Vgcc_ntox86 -c fred.c > err 2>&1
or
qcc -Vgcc_ntox86 -c fred.c 2>&1 | tee err
John
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:8sfqc4$iqj$> 2@nntp.qnx.com> …
For now you’ll have to redirect. I might add the capability to qcc
though, since this feature was pretty useful.The account for depositing bribes is … ;v)
J. Scott Franko <> jsfranko@switch.com> > wrote:
Anyone know off the top of their head, if there is a facility in GNU to
save compiler messages to a file as well as put them to the screen, like
watcom put them in *.err files where the * was the c source filename
being compiled? Do I have to do something kludgy like redirect the
output to a file?Scott
\