POV-Ray : Newsgroups : povray.programming : writing gcc error messages stdout/stderr (Nic) Server Time
26 Apr 2024 12:19:26 EDT (-0400)
  writing gcc error messages stdout/stderr (Nic) (Message 1 to 1 of 1)  
From: alphaQuad
Subject: writing gcc error messages stdout/stderr (Nic)
Date: 29 Dec 2007 11:40:00
Message: <web.47767834ff655b93fc36fa300@news.povray.org>
Nicolas: hope you're reading this.

>>Hi,
>>
>>assuming you want to read the messages after running make, you can use
>>"make 1>&messages.txt 2>&1".
>>
>>hope that helps.

>The number before the redirection represents the stream to be redirected,
>where 1 = stdout and and 2 = stderr. The &1 represents the previously-
>mentioned messages.txt, so the command means redirect messages
>written to stdout and stderr to messages.txt. The 1> is not necessary,
>since by default  '>' redirects stdout.

>Since gcc writes its warnings and error messages to stderr, your text files
>contain neither. You will see only the commands that make executed.


A++ for effort. Thank you. But no working example has been achieved.

tried every combination of 1>&messages.txt 2>&1

Ampersands always become part of the filename.
adding a 1 or a 2 is never accepted - "no rule to make target '2' Stop."
>>mess.txt = stdout
>mess.txt >mess2.txt = stdout

"You will see only the commands that make executed."
yes I noticed that.

Nicolas:
Do you have a working example on your end?


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.