From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 102078 invoked by alias); 28 Feb 2016 08:31:30 -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 102067 invoked by uid 89); 28 Feb 2016 08:31:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=U*aph, aph@redhat.com, aphredhatcom, H*r:SMTPS 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 (AES128-SHA encrypted) ESMTPS; Sun, 28 Feb 2016 08:31:28 +0000 Received: from localhost (x4d0cd8b4.dyn.telefonica.de [77.12.216.180]) by mx.zohomail.com with SMTPS id 1456648286321702.9389821937075; Sun, 28 Feb 2016 00:31:26 -0800 (PST) References: <87k2qlgtd0.fsf@elephly.net> <56237454.1000808@redhat.com> <874mh9j2rv.fsf@elephly.net> <56320DAB.3040207@redhat.com> <8737wtj1ny.fsf@elephly.net> <5672C053.9050905@redhat.com> <87si222dda.fsf@elephly.net> <569629C8.8070400@redhat.com> <874mcudrt4.fsf@elephly.net> <56D217E7.2030202@redhat.com> User-agent: mu4e 0.9.13; emacs 24.5.1 From: Ricardo Wurmus To: Andrew Haley Cc: java@gcc.gnu.org Subject: Re: GCJ 4.9.3 on mips64el-linux failing to build Ant. In-reply-to: <56D217E7.2030202@redhat.com> Date: Sun, 28 Feb 2016 08:31:00 -0000 Message-ID: <871t7xdyn9.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Zoho-Virus-Status: 1 X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00002.txt.bz2 Andrew Haley writes: > On 27/02/16 16:46, Ricardo Wurmus wrote: >> is there anything else I can provide to assist you in identifying >> the problem with GCJ on ARM and MIPS? > > Please forgive me if this sounds harsh... > > Hmm. I can't fix it without access to hardware, and I'm very busy. I > can't really prioritize this over everything else. I'm afraid you're > going to have to fix it yourself or find someone who also needs GCJ to > work on MIPS. No problem at all. Thanks for letting me know. I don’t have MIPS hardware myself, but I could gain access to the build machine on which the build fails and play around with it. Do you have any ideas on what *might* be wrong to help me getting started? ~~ Ricardo