Re: GCJ 4.9.3 on mips64el-linux failing to build Ant.

[Andrew Haley <aph@redhat.com>]

On 13/01/16 06:38, Ricardo Wurmus wrote:
> 
> Andrew Haley <aph@redhat.com> writes:
> 
>> On 10/29/2015 12:32 PM, Ricardo Wurmus wrote:
>>> Andrew Haley <aph@redhat.com> writes:
>>>
>>>> On 10/29/2015 12:08 PM, Ricardo Wurmus wrote:
>>>>> Here’s the complete log that I get when building GCJ 4.9.3 and running
>>>>> the tests:
>>>>>
>>>>>     http://hydra.gnu.org/build/758888/log/raw
>>>>
>>>> I can't see the output of the libjava testsuite.  "make check-target-libjava"
>>>> should do it.
>>>
>>> Here’s the libjava testsuite output:
>>
>> No, the actual testsuite output.  It's in a logfile.
> 
> Attached is “libjava.log” from the directory
> “build/arm-unknown-linux-gnueabihf/libjava/testsuite/”.  One obvious
> problem according to the log is this:
> 
>     gcj: error trying to exec 'ecj1': execvp: No such file or directory
> 
> GCJ is configured with the following flags (in addition to the usual GCC
> flags):
> 
>     "--enable-java-home"
>     "--enable-gjdoc"
>     "--with-ecj-jar=ecj-4.9.jar"
>     "--enable-languages=java"
> 
> “ecj-4.9.jar” is the one downloaded from
> <ftp://sourceware.org/pub/java/ecj-4.9.jar>.  I cannot build it from
> source because that would require a JDK — GCJ is the first JDK I’m
> building on ARM and MIPS.  Is this a problem?  Is “ecj-4.9.jar” portable
> or does it need to be cross-built for other platforms?

It's portable.  There's no particular problem with running the libgcj
testsuite from bytecode files, so I would not worry about that.  However,
there are some serious problems in the testsuite output which indicate
that gcj has some bugs on this platform.

Andrew.