From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30144 invoked by alias); 19 Nov 2001 17:48:39 -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 30060 invoked by uid 61); 19 Nov 2001 17:48:38 -0000 Date: Tue, 13 Nov 2001 15:16:00 -0000 Message-ID: <20011119174838.30059.qmail@sourceware.cygnus.com> To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, georg.wild@gmx.de, java-prs@gcc.gnu.org, tromey@gcc.gnu.org From: tromey@gcc.gnu.org X-Mailer: gnatsweb 2.9.2 Subject: Re: java/4804: jar not found X-SW-Source: 2001-11/txt/msg00300.txt.bz2 List-Id: Synopsis: jar not found State-Changed-From-To: analyzed->closed State-Changed-By: tromey State-Changed-When: Mon Nov 19 09:48:37 2001 State-Changed-Why: This problem is caused by re-running autoconf, which shouldn't happen. In the short term the fix is to simply back out the configure changes. In the long term the fix is to port to the latest autoconf and automake. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4804&database=gcc