From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1542 invoked by alias); 26 Jan 2007 02:23:26 -0000 Received: (qmail 1520 invoked by uid 48); 26 Jan 2007 02:23:26 -0000 Date: Fri, 26 Jan 2007 02:23:00 -0000 Message-ID: <20070126022326.1519.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/30591] Cross build fails because native gcj needed to build ecjx 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-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2007-q1/txt/msg00199.txt.bz2 ------- Comment #2 from tromey at gcc dot gnu dot org 2007-01-26 02:23 ------- FWIW I don't think we want to fail outright if no suitable gcj is found. The whole business with compiling and installing ecj.jar is a convenience, not a strict necessity. The user can always make his own ecj1 "somehow" (e.g, I use a shell script). So one idea would be to look for a gcj for the build machine, and if not found, disable compilation of ecjx. What do you think? -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-01-26 02:23:25 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591