🚀 go-pugleaf

On Mon, 4 Jun 2001 10:41:30 +0300, Naftali Salz <salz@menix.bgu.ac.il> wrote:
> 
> 
> if you use tcsh use gcc -o testprog.c | & less
> then you can scroll up and down the error list and when you are done
> simply press Q.
> 
> 
> 
> On 26 May 2001, loki wrote:
> 
>> David. E. Goble <goble@gtech> wrote unto us:
>> >Hi all;
>> >
>> >I am just beginning to try programming in linux (redhat).
>> >
>> >My problem is when I use gcc ...etc it produces a scolling list of
>> >errors. How can I move or pipe the errors to a file. ie something like
>> >
>> >	gcc -o hello.c > error.txt?

If you use the bash shell (most common) then do this ?

gcc -0 hello.c 2> error.txt

The "2" tells the bash shell to re direct *errors* to "error.txt"

(page 98, "Running Linux"  O'Rielly and assoc)

>>
>> As a final tip to add to the others, sometimes it is nice to both view and
>> save the output of a program.  The little utility 'tee' is handy for this.
>> You can use it like this:
>>
>> gcc -o testprog test.c 2>&1 | tee out.log
>>
>> The 'tee' program will save what it receives on standard input to the named
>> file, as well as printing it to the screen.  This often gives you the best
>> of both worlds with regard to viewing and saving of errors.
>>
>>
>> --
>>     loki
>> eloki/at/dingoblue.net.au
>>
>> Dare I disturb the universe?  You bet I do! :)
>>
>>
> 


-- 
Kind Regards
Terry
--
****                                                  ****
   My Desktop is powered by GNU/Linux.   
   1972 Kawa Mach3, 1974 Kawa Z1B, .. 15 more road bikes..
   Current Ride ...  a 94 Blade
Free Micro burner: http://jsno.downunder.net.au/terry/          
** Registration Number: 103931,  http://counter.li.org **