public inbox for
 help / color / mirror / Atom feed
From: Ricardo Wurmus <>
To: Andrew Haley <>
Subject: Re: GCJ 4.9.3 on mips64el-linux failing to build Ant.
Date: Thu, 29 Oct 2015 12:08:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Andrew Haley <> writes:

> It looks to me like gcj is non-functional.  Are you building GCC 4.9.3?
> Please run the gcj test suite (make check-target-libjava) to see if it
> is broken.

Yes, I built GCJ as a variant of GCC 4.9.3 (disabling all other
languages but Java).  Surprisingly, “make check-target-libjava” passes
on MIPS, but GCJ is not working as can be seen when attempting to build

Here’s the complete log that I get when building GCJ 4.9.3 and running
the tests:
The beginning of the test phase is marked by “starting phase `check'”.
I don’t see anything suspicious in the test output.

Here’s the latest failing build of Ant on MIPS:

The errors are the same as before:

    1. ERROR in /tmp/nix-build-ant-1.9.4.drv-0/apache-ant-1.9.4/src/main/org/apache/tools/bzip2/ (at line 121)
    QSORT_STACK_SIZE cannot be resolved to a variable

~~ Ricardo

  reply	other threads:[~2015-10-29 12:08 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 [this message]
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

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:

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

  git send-email \ \ \ \ \

* 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).