From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24694 invoked by alias); 15 Sep 2004 04:02:03 -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 24650 invoked from network); 15 Sep 2004 04:01:57 -0000 Received: from unknown (HELO motgate5.mot.com) (144.189.100.105) by sourceware.org with SMTP; 15 Sep 2004 04:01:57 -0000 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate5.mot.com (8.12.11/Motgate2) with ESMTP id i8F42BX5009268 for ; Tue, 14 Sep 2004 21:02:11 -0700 (MST) Received: from latour.waar.labs.mot.com (latour.waar.labs.mot.com [173.23.133.73]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i8F41t1J002154 for ; Tue, 14 Sep 2004 23:01:55 -0500 Received: from latour.waar.labs.mot.com (localhost.waar.labs.mot.com [127.0.0.1]) by latour.waar.labs.mot.com (8.13.1/8.13.1) with ESMTP id i8F41rhL044081; Tue, 14 Sep 2004 23:01:53 -0500 (CDT) (envelope-from rittle@latour.waar.labs.mot.com) Received: (from rittle@localhost) by latour.waar.labs.mot.com (8.13.1/8.13.1/Submit) id i8F41rWZ044080; Tue, 14 Sep 2004 23:01:53 -0500 (CDT) (envelope-from rittle) Date: Wed, 15 Sep 2004 06:38:00 -0000 From: Loren James Rittle Message-Id: <200409150401.i8F41rWZ044080@latour.waar.labs.mot.com> To: gcc@gcc.gnu.org Subject: Re: Obsolete building in source dir? In-Reply-To: References: <00f801c497a2$e2deb9c0$92b92997@bagio> <20040914121705.A32238@synopsys.com> <200409141943.i8EJhpx2017814@greed.delorie.com> Organization: Applications, Content and Services CoE (IL02/2240), Motorola Labs Cc: rittle@latour.waar.labs.mot.com X-SW-Source: 2004-09/txt/msg00899.txt.bz2 > I would consider it a technical matter, not a big enough issue for the > SC to step in. [...] Agreed, the documentation already tells users how to get best results. Those that refuse to read it or believe it, can report a bug when their build stops half-way through. That is how all bugs, not seen by gcc developers, are fixed. In any event: http://people.freebsd.org/~ljrittle/daily-gcc-bootstrap-reports/ref4/STATUS gcc 3.1 20020513, objdir configuration, gmake, bootstrapped OK gcc 3.1 20020513, srcdir configuration, gmake, bootstrapped OK gcc 3.1.1 , objdir configuration, gmake, bootstrapped OK gcc 3.1.1 , srcdir configuration, gmake, bootstrapped OK gcc 3.2 20020813, objdir configuration, gmake, bootstrapped OK gcc 3.2 20020813, srcdir configuration, gmake, bootstrapped OK gcc 3.2.1 , objdir configuration, gmake, bootstrapped OK gcc 3.2.1 , srcdir configuration, gmake, bootstrapped OK gcc 3.2.2 20030129, objdir configuration, gmake, bootstrapped OK gcc 3.2.2 20030129, srcdir configuration, gmake, bootstrapped OK gcc 3.3 20030421, srcdir configuration, gmake, bootstrapped OK gcc 3.3 20030421, objdir configuration, gmake, bootstrapped OK gcc 3.3 , srcdir configuration, gmake, bootstrapped OK gcc 3.3 , objdir configuration, gmake, bootstrapped OK gcc 3.3.1 20030803, srcdir configuration, gmake, bootstrapped OK gcc 3.3.1 20030803, objdir configuration, gmake, bootstrapped OK [This testing machine non-functional during 3.3.2 & 3.3.3 & 3.4 release cycles.] gcc 3.4.1 , srcdir configuration, gmake, bootstrapped OK gcc 3.4.1 , objdir configuration, gmake, bootstrapped OK gcc 3.4.2 , srcdir configuration, gmake, bootstrapped OK gcc 3.4.2 , objdir configuration, gmake, bootstrapped OK (The dated versions are close to a release.) I have no idea about the state of mainline but... Once a 4.0.0 branch is cut and a daily "srcdir configuration" tester is moved to it, I'm sure we will fix any bugs before the release. If we don't, then I will propose the needed documentation patch that I always pull out whenever it is required... Regards, Loren