From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26718 invoked by alias); 29 Mar 2002 19:16:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 26698 invoked by uid 71); 29 Mar 2002 19:16:01 -0000 Date: Fri, 29 Mar 2002 11:16:00 -0000 Message-ID: <20020329191601.26697.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Tom Tromey Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64 Reply-To: Tom Tromey X-SW-Source: 2002-03/txt/msg01205.txt.bz2 List-Id: The following reply was made to PR java/6092; it has been noted by GNATS. From: Tom Tromey To: "Kaveh R. Ghazi" Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64 Date: 29 Mar 2002 12:14:25 -0700 >>>>> "Kaveh" == Kaveh R Ghazi writes: Kaveh> I looked at last night's testrun to see the context around each Kaveh> failure. Unfortunately there aren't any useful error messages, it Kaveh> just compiles/PASSes and then spawn FAILs the run. I've included a Kaveh> bunch of them here using "grep -B 3 ^FAIL libjava.log" so you can see Kaveh> what I mean. Maybe running dejagnu with `--verbose' will give more information. The libjava test suite doesn't remove an executable if it fails. So you could also try running the executable by hand to see if it fails outside the test suite. (This isn't always perfectly accurate due to environmental differences; for instance the test suite sets LD_LIBRARY_PATH.) Thanks for looking at this. Tom