From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15662 invoked by alias); 14 Nov 2004 00:02:40 -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 15234 invoked from network); 14 Nov 2004 00:02:28 -0000 Received: from unknown (HELO vexpert.dbai.tuwien.ac.at) (128.131.111.2) by sourceware.org with SMTP; 14 Nov 2004 00:02:28 -0000 Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 0564E13794; Sun, 14 Nov 2004 01:02:28 +0100 (CET) Date: Sun, 14 Nov 2004 00:05:00 -0000 From: Gerald Pfeifer To: Mike Stump Cc: gcc@gcc.gnu.org, java@gcc.gnu.org, David O'Brien Subject: Re: configure, CFLAGS, and libjava In-Reply-To: <2ED5BE2A-35CC-11D9-822C-003065BDF310@apple.com> Message-ID: References: <2ED5BE2A-35CC-11D9-822C-003065BDF310@apple.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SW-Source: 2004-11/txt/msg00467.txt.bz2 On Sat, 13 Nov 2004, Mike Stump wrote: > Not limited to libjava... All of it is, uhm, what's the word, unfortunate. > It triggers too often, and just doesn't do the right thing, an rm -rf > followed by another build would be preferable, as then it would actually > build all the time. Well, it is much worse than that! For libjava, this failure reproducibly happens when building in a pristine build tree from pristine sources. Gerald