From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16873 invoked by alias); 31 Mar 2006 23:30:59 -0000 Received: (qmail 16853 invoked by uid 48); 31 Mar 2006 23:30:58 -0000 Date: Fri, 31 Mar 2006 23:30:00 -0000 Message-ID: <20060331233058.16852.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/25847] libjava build doesn't stop when there is a fatal error In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "tromey at gcc dot gnu dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q1/txt/msg00482.txt.bz2 List-Id: ------- Comment #3 from tromey at gcc dot gnu dot org 2006-03-31 23:30 ------- Is there a reasonable way to detect good failures versus bad failures here? We definitely want to ignore cases where gcj-dbtool fails due to things like not having mmap available. Perhaps the thing to do is let it fail and then catch it during 'make check'. -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25847