public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Andrew Haley <aph@redhat.com>
Cc: GCC Java <java@gcc.gnu.org>
Subject: Re: Trouble building gcj 4.8.1
Date: Tue, 25 Jun 2013 14:10:00 -0000	[thread overview]
Message-ID: <CANEZrP1_ChOzW9jLw=Qtx0T43GytbFZpWc7KaxGh_wFP7nD38g@mail.gmail.com> (raw)
In-Reply-To: <51C9A389.6030000@redhat.com>

> No, you have to put it in your own path.  It does say so in the
> instructions.

Ah. The docs say:

"If this option is given, the ‘libjava’ build will create and install
an ecj1 executable which uses this jar file at runtime.  If this
option is not given, but an ecj.jar file is found in the topmost
source tree at configure time, then the ‘libgcj’ build will create and
install ecj1, and will also install the discovered ecj.jar into a
suitable place in the install tree."

I interpreted "create and install" to mean it'll be put into bin by
"make install", it might be clearer if it said explicitly that you
have to copy it or put the script there yourself.


My goal with all this is to compile and run a Java program as a MIPS
program that is as small as possible, which I intend to do by:

 - Compiling with GCJ, as MIPS supporting Java VMs are rare
 - Enabling as many dead code elimination passes as possible,
including LTO with a static libgcj

in the hope that I can get a nice small, self contained binary out of the end.

As a bonus, I'd also like to enable usage of a library that this
program uses from C++ codebases using CNI, although that's secondary
right now.

Could you maybe elaborate on the ninja stuff? Why are there two copies
of these core classes? How much effort is it to fix things up - are we
talking a few days here, a few weeks, a few months?

  reply	other threads:[~2013-06-25 14:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 13:21 Mike Hearn
2013-06-24 16:48 ` Mike Hearn
2013-06-24 17:04   ` Andrew Haley
2013-06-24 17:17     ` Mike Hearn
2013-06-24 17:26       ` Andrew Haley
2013-06-24 20:36         ` Matthias Klose
2013-06-25 13:39         ` Mike Hearn
2013-06-25 13:53           ` Mike Hearn
2013-06-25 14:07             ` Andrew Haley
2013-06-25 14:05           ` Andrew Haley
2013-06-25 14:10             ` Mike Hearn [this message]
2013-06-25 14:12               ` Andrew Haley
2013-06-25 14:15                 ` Mike Hearn
2013-06-25 14:21                   ` Andrew Haley
2013-06-28  1:28                     ` Andïï
2013-06-28  9:06                       ` Andrew Haley
2013-07-02 14:53                     ` Bryce McKinlay
     [not found]                       ` <CANEZrP1tLxpu818cFGdgma+RVL32yRJJUOyb5m8QF=mhTZVueg@mail.gmail.com>
2013-07-03 13:43                         ` Mike Hearn
2013-07-03 13:47                           ` Andrew Haley
2013-07-03 21:31                             ` Bryce McKinlay
2013-06-25 14:05           ` 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='CANEZrP1_ChOzW9jLw=Qtx0T43GytbFZpWc7KaxGh_wFP7nD38g@mail.gmail.com' \
    --to=mike@plan99.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).