From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19612 invoked by alias); 5 Mar 2014 17:32:48 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 19597 invoked by uid 89); 5 Mar 2014 17:32:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.3 required=5.0 tests=AFFECTIONATE_BODY,AWL,BAYES_50,DEAR_SOMETHING,FREEMAIL_FROM,KAM_MXURI,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 X-HELO: omr-m03.mx.aol.com Received: from omr-m03.mx.aol.com (HELO omr-m03.mx.aol.com) (64.12.143.77) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 05 Mar 2014 17:32:47 +0000 Received: from mtaout-mce02.mx.aol.com (mtaout-mce02.mx.aol.com [172.29.27.206]) by omr-m03.mx.aol.com (Outbound Mail Relay) with ESMTP id 331E77003620C for ; Wed, 5 Mar 2014 12:32:45 -0500 (EST) Received: from [192.168.0.9] (cpe-69-133-204-177.cinci.res.rr.com [69.133.204.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaout-mce02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id C66A2380000AA for ; Wed, 5 Mar 2014 12:32:44 -0500 (EST) Message-ID: <53175FBD.4040408@aol.com> Date: Wed, 05 Mar 2014 17:34:00 -0000 From: Tim Prince Reply-To: tprince@computer.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: logging gcc messages References: <53175EDB.6060207@uni-bremen.de> In-Reply-To: <53175EDB.6060207@uni-bremen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit x-aol-global-disposition: G x-aol-sid: 3039ac1d1bce53175fbc7b10 X-AOL-IP: 69.133.204.177 X-SW-Source: 2014-03/txt/msg00017.txt.bz2 On 3/5/2014 12:28 PM, Michael Markowsky wrote: > Dear Madam , Dear Sir > > I use gcc on a linux - system and wish to save the compiler messages for > further analysation. > so something like gcc filename.cpp>result.txt didn´t work > > Any idea > Check which shell you are running and look up how to redirect stderr to your file; e.g. for bash et al. gcc filename.cpp>result.txt 2>&1 -- Tim Prince