From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-52255-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 14436 invoked by alias); 22 Feb 2013 09:45:14 -0000
Received: (qmail 14426 invoked by uid 22791); 22 Feb 2013 09:45:12 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from snt0-omc4-s37.snt0.hotmail.com (HELO snt0-omc4-s37.snt0.hotmail.com) (65.55.90.240)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Feb 2013 09:45:07 +0000
Received: from SNT139-W62 ([65.55.90.201]) by snt0-omc4-s37.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);	 Fri, 22 Feb 2013 01:45:07 -0800
X-EIP: [Ftq5S6fYVyMRopHyONQnlDHsfUoaoXz4]
Message-ID: <SNT139-W621CB4A3409C9FCE9BA81BADF00@phx.gbl>
From: Michael Young <mikado_282@hotmail.com>
To: <gcc-help@gcc.gnu.org>
Subject: RE: Testing gcj/libgcj with mauve
Date: Fri, 22 Feb 2013 09:45:00 -0000
In-Reply-To: <SNT139-W396FB6095E5229D1D406B0ADF70@phx.gbl>
References: <SNT139-W2747390D687EB927B60AE5ADF50@phx.gbl>,<512496F9.4000706@redhat.com>,<SNT139-W3DDD7ECBF827F794ED81AADF70@phx.gbl>,<SNT139-W396FB6095E5229D1D406B0ADF70@phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
X-SW-Source: 2013-02/txt/msg00150.txt.bz2


I again did a clean build, with a fresh mauve directory. This time, I
didn't use the MAUVEDIR variable for the make invocation, but put a
symlink "mauve" in <SRC_DIR>/gcc-4.7.2/libjava/testsuite/libjava.mauve
that points to my mauve directory. This yielded the same failures as
previous attempts (unrecognized configure option "--with-gcj" and an
invalid make target "classes.stamp" (i.e., no rule to make it)).

At this point, I have run out of reasonable ideas to try to get the
gcj/libgcj testing using mauve to work.=A0 While I certainly may be
doing something wrong, I'm beginning to wonder if these failures may
be due to bitrot of this functionality.=A0 If anyone is still using mauve
to test gcj/libgcj builds or has any insight, I'd greatly appreciate
any feedback.

Thanks,
=A0 Mike
=20=09=09=20=09=20=20=20=09=09=20=20