From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104767 invoked by alias); 18 Jan 2017 20:59:22 -0000 Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org Received: (qmail 104757 invoked by uid 89); 18 Jan 2017 20:59:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL,URIBL_RHS_DOB autolearn=no version=3.3.2 spammy=mes, unavoidable, Hx-languages-length:1492, 3801 X-HELO: sender163-mail.zoho.com Received: from sender163-mail.zoho.com (HELO sender163-mail.zoho.com) (74.201.84.163) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 18 Jan 2017 20:59:11 +0000 Received: from localhost (x4d0c9600.dyn.telefonica.de [77.12.150.0]) by mx.zohomail.com with SMTPS id 1484773144635169.25182697599837; Wed, 18 Jan 2017 12:59:04 -0800 (PST) References: <9335b6e8-ed7f-1e8d-4022-656da4681770@redhat.com> <59a501d2701f$b1bb1290$153137b0$@yahoo.com> <87ziiq937c.fsf@elephly.net> <59dc01d2704c$0d4ea910$27ebfb30$@yahoo.com> <878tq86rjx.fsf@elephly.net> <92b25477-ed9d-f35e-a9b4-2cb90e425cbd@ubuntu.com> User-agent: mu4e 0.9.18; emacs 25.1.1 From: Ricardo Wurmus To: Matthias Klose Cc: Andrew Haley , bill.chatfield@yahoo.com, 'mohan NMH' , java@gcc.gnu.org Subject: Re: Fwd: gcj can not import packages In-reply-to: <92b25477-ed9d-f35e-a9b4-2cb90e425cbd@ubuntu.com> Date: Wed, 18 Jan 2017 20:59:00 -0000 Message-ID: <8760lc6q5n.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-01/txt/msg00009.txt.bz2 Matthias Klose writes: > yes, you need some trusted binaries. For example, there are various Linux > distributions which provide these binaries. And even if you want to build for a > target that doesn't have binaries, you can first build a native openjdk on your > build platform, and then cross-build for your target. I built several Linux > architectures this way ... The Bootstrappable Builds project[1] ties to remove the number of trusted binaries to bootstrap a modern system. One way to get there is to have a bootstrap path that leads to the unavoidable C compiler. And even the C compiler doesn’t *have* to be a trusted binary. The Mes project[2] tries to build a C compiler using a minimal, hand-verifyable Scheme implementation, for example. I just find it sad to see GCJ go, because it makes it quite a bit harder to build the OpenJDK without a trusted JDK. Relying on the last release of GCC that included the GCJ sources isn’t a viable long-term solution, because, as experience has shown, build systems of the past become unsupported and harder to satisfy as time passes. It is, for example, quite a challenge to build the GNU Pascal compiler (needed to bootstrap the self-hosted Freepascal compiler from source) from a decade back with a modern toolchain. [1]: http://bootstrappable.org [2]: https://gitlab.com/janneke/mes -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net