From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3486 invoked by alias); 23 Sep 2010 12:02:26 -0000 Received: (qmail 3469 invoked by uid 22791); 23 Sep 2010 12:02:25 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Sep 2010 12:02:18 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o8NC2GkL016583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Sep 2010 08:02:17 -0400 Received: from zebedee.pink (ovpn-113-95.phx2.redhat.com [10.3.113.95]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o8NC2FSM018653; Thu, 23 Sep 2010 08:02:16 -0400 Message-ID: <4C9B41C6.2060901@redhat.com> Date: Thu, 23 Sep 2010 12:02:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: Josh Marinacci CC: java@gcc.gnu.org Subject: Re: Advice on compiling GCJ for ARM References: <3D92DBFC-92B6-439F-B565-BB29CF1FC04A@marinacci.org> <4C9872F4.90409@redhat.com> <4C99B9A8.5080008@redhat.com> <90E1FBED-77D8-4889-9E70-531174468D92@marinacci.org> In-Reply-To: <90E1FBED-77D8-4889-9E70-531174468D92@marinacci.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2010-09/txt/msg00014.txt.bz2 On 22/09/10 16:05, Josh Marinacci wrote: >> 4.5 branch: more or less 4.5.1. >> >>> & glibc are you using? >> >> Hmmm, dunno. Whatever is in Fedora 12: glibc-2.11.2-1. > > Ah, so you are compiling against a premade glibc for your target > OS. That was the part I was missing. That's always the easiest way to do it. Build gcc against a system that works, and you have a complete cross-gcc. You can use that cross-gcc to make your target OS; that way you have a fully working cross-gcc from the start. Andrew.