public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org
Subject: Re: GCJ 4.9.3 on mips64el-linux failing to build Ant.
Date: Sun, 28 Feb 2016 08:31:00 -0000	[thread overview]
Message-ID: <871t7xdyn9.fsf@elephly.net> (raw)
In-Reply-To: <56D217E7.2030202@redhat.com>


Andrew Haley <aph@redhat.com> 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

      reply	other threads:[~2016-02-28  8:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 19:58 Ricardo Wurmus
2015-10-18 10:28 ` Andrew Haley
2015-10-29 12:08   ` Ricardo Wurmus
2015-10-29 12:14     ` Andrew Haley
2015-10-29 12:32       ` Ricardo Wurmus
2015-12-17 13:46         ` rekado
2015-12-17 14:02         ` Andrew Haley
2015-12-17 14:04           ` Andrew Haley
2016-01-13  6:40           ` Ricardo Wurmus
2016-01-13  6:48             ` Ricardo Wurmus
2016-01-13  9:39               ` Andrew Haley
2016-01-13 10:41             ` Andrew Haley
2016-02-27 16:46               ` Ricardo Wurmus
2016-02-27 21:41                 ` Andrew Haley
2016-02-28  8:31                   ` Ricardo Wurmus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t7xdyn9.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).