From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24417 invoked by alias); 5 Jan 2003 17:37:22 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 24361 invoked from network); 5 Jan 2003 17:37:02 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by 209.249.29.67 with SMTP; 5 Jan 2003 17:37:02 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva.cipe.redhat.com [10.0.1.10]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id h05HakY24964; Sun, 5 Jan 2003 12:36:46 -0500 Received: from free.redhat.lsd.ic.unicamp.br (localhost.localdomain [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.6/8.12.6) with ESMTP id h05Haipx009080; Sun, 5 Jan 2003 15:36:44 -0200 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.6/8.12.6/Submit) id h05HagVU009070; Sun, 5 Jan 2003 15:36:42 -0200 To: Neil Booth Cc: Erik Schnetter , Toon Moene , gcc@gcc.gnu.org Subject: Re: g77 -fixed-line-length-none -x f77-cpp-input -c blah.f References: <200301041820.38821.schnetter@uni-tuebingen.de> <20030104193247.GA4976@daikokuya.co.uk> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Sun, 05 Jan 2003 17:59:00 -0000 In-Reply-To: <20030104193247.GA4976@daikokuya.co.uk> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-01/txt/msg00222.txt.bz2 On Jan 4, 2003, Neil Booth wrote: > "cpp" is just a driver and never did any preprocessing. The > preprocessing has been done by either cccp (2.95.x), cpp0 / tradcpp0 > combo (3.0), cc1 / tradcpp0 combo (3.1, 3.2) or cc1 alone (>= 3.3). > I think 8-) cccp was first renamed to cpp, and only then to cpp0. I believe gcc 2.96ish snapshots (or was it egcs?) used cpp for the internal name, which caused a lot of grief in case gcc failed to find the internal cpp, searched the PATH, found the cpp driver and ran it. The cpp driver then happily searched for an internal cpp, failed, and then searched the PATH, finding the cpp driver, which it then proceeded to start, and so on, and so forth, until the whole thing blew up. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer