From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17002 invoked by alias); 3 Apr 2002 02:47:14 -0000 Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org Received: (qmail 16967 invoked from network); 3 Apr 2002 02:47:11 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by sources.redhat.com with SMTP; 3 Apr 2002 02:47:11 -0000 Received: from creche.cygnus.com (ta0195.peakpeak.com [204.144.244.195]) by gash2.peakpeak.com (8.9.3/8.9.3) with ESMTP id TAA10239; Tue, 2 Apr 2002 19:47:06 -0700 Received: (from tromey@localhost) by creche.cygnus.com (8.9.3/8.9.3) id TAA23161; Tue, 2 Apr 2002 19:48:58 -0700 To: Rainer Orth Cc: Anthony Green , Adam Megacz , java@gcc.gnu.org Subject: Re: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap failure) References: <200203132014.VAA27030@tamarinde.TechFak.Uni-Bielefeld.DE> <86henk3xp5.fsf@megacz.com> <15503.54620.761421.899604@xayide.TechFak.Uni-Bielefeld.DE> <867kog3vv5.fsf@megacz.com> <1016062833.12572.595.camel@dhcppc2> <15504.33266.2722.237598@xayide.TechFak.Uni-Bielefeld.DE> <87adt9y0jd.fsf@creche.redhat.com> <15506.26755.691929.593580@xayide.TechFak.Uni-Bielefeld.DE> <87n0x9wkdq.fsf@creche.redhat.com> <15506.31114.453333.47693@xayide.TechFak.Uni-Bielefeld.DE> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Do I hear th' SPINNING of various WHIRRING, ROUND, and WARM WHIRLOMATICS?! Date: Tue, 02 Apr 2002 18:49:00 -0000 In-Reply-To: Rainer Orth's message of "Fri, 15 Mar 2002 23:45:30 +0100 (MET)" Message-ID: <87elhxwl7p.fsf@creche.redhat.com> X-SW-Source: 2002-04/txt/msg00025.txt.bz2 >>>>> "Rainer" == Rainer Orth writes: I didn't see a reply to this. Rainer> One new failure is the Primes test: there's a gc message Rainer> interspersed with the (correct) output: Rainer> Needed to allocate blacklisted block at 0x1f9000 Rainer> Maybe this can be disabled in boehm-gc or ignored somehow: Rainer> unlike the test output, it is written to stderr, not stdout. This message is pretty much expected. There's some discussion of this on the list a while back. Adding code to the test suite to let us ignore this has been on my to-do list forever. Tom