public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Andrew Haley <aph@redhat.com>
Cc: Matthijs van de Water <matthijs.van.de.water@gmail.com>,
		java@gcc.gnu.org
Subject: Re: ecj1 in cross-compile
Date: Wed, 11 Jun 2008 16:32:00 -0000	[thread overview]
Message-ID: <484FFE0A.8030501@avtrex.com> (raw)
In-Reply-To: <484F8E26.2070203@redhat.com>

Andrew Haley wrote:
> Matthijs van de Water wrote:
>
>   
>> I've got my GCC 4.3 toolchain working ok now, but for some reason I
>> fail to get an ecj1 binary.
>>
>> I'm cross-compiling for ARM and I've tried --with-ecj-jar=XXX (which
>> doesn't result in an ecj1) and also tried putting ecj.jar in my build
>> dir (which complains about a missing java compiler).
>> I must be doing something wrong, but I'm not sure what.
>>
>> I expect an i686 ecj1 binary to be compiled from the ecj-latest.jar
>> that I download in my build. Preferably standalone, like the Ubuntu
>> one.
>> The build machine doesn't have an i686 GCJ or JAVAC installed, is that
>> a problem?
>>
>> What am I missing?
>>     
>
> I don't know how you think this is going to work.  ecj1 is a Java program
> and thus it needs some sort of Java runtime library.  You are going to need
> an i686 gcj installed.  

That's right.  It is a new requirement for GCC-4.3 cross compilers.
Either install a native build of gcj/libgcj in your PATH, or as Andrew
suggested use the little shell script to invoke the jar file.

You have to be careful though, if you may not always want a native
GCC-4.3 in your PATH, perhaps only when invoking the cross compiler.
You could just copy or link the native ecj1 to the cross compiler bin
directory.

David Daney

  reply	other threads:[~2008-06-11 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  7:37 Matthijs van de Water
2008-06-11  8:35 ` Andrew Haley
2008-06-11 16:32   ` David Daney [this message]
2008-08-13 20:51     ` Daniel Andrzejewski
2008-08-14 10:08       ` Andrew Haley
2008-08-14 14:13         ` Daniel Andrzejewski
2008-08-14 14:42           ` Andrew Haley
2008-08-14 15:40             ` Daniel Andrzejewski
2008-08-14 16:11               ` Andrew Haley

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=484FFE0A.8030501@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=matthijs.van.de.water@gmail.com \
    /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).