public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: "Alon Bar-Lev" <alon.barlev@gmail.com>
Cc: "Andrew Cowie" <andrew@operationaldynamics.com>,
	 gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] icedtea6 bootstrap
Date: Wed, 17 Sep 2008 23:01:00 +0100	[thread overview]
Message-ID: <17c6771e0809171501l78109c61s567f2da7e07273f1@mail.gmail.com> (raw)
In-Reply-To: <9e0cf0bf0809171119r215edc53mf741320f6ac39051@mail.gmail.com>

2008/9/17 Alon Bar-Lev <alon.barlev@gmail.com>:
> On 9/17/08, Andrew John Hughes <gnu_andrew@member.fsf.org> wrote:
>> First of all, there is no need to go to such lengths removing gcj afterwards.
>>  It's not going to hurt to leave it on.
>
> It takes a lot of resources (disk, time rebuilding, unused components).
> So there is a reason to keep system as small as possible.
>

Err.. time rebuilding is part of the reason _not_ to remove it.
Applications like ecj benefit from being natively compiled by gcj in
my experience.
There is a gcj USE flag in Gentoo for this purpose.

You're probably talking about ~150mb vs. a long re-build time.  I'd take the
150mb and potential future use, especially with today's hard disc sizes.
gcc still takes a while to build even on new machines.

>>  Also, the build depends on jdk >= 1.5 already, so CACAO or JamVM would
>>  do the job fine.  But you'd have similar bootstrap issues, because these
>>  require GNU Classpath and that requires ecj, etc.
>
> So gcj is the best alternative. But what happens if gcc stops
> providing this in favor of OpenJDK?
>

Not likely anytime in the near future.

>>  Building a Java environment can be a nightmare to be honest :)
>>  I guess the only non-GCJ way would be to use Jikes, then an older Classpath
>>  to get ecj working, then build the new ones.
>
> I guess I am asking that icedtea6 does not have such boostrap in package...

That's pretty much impossible, unless you plan to write a compiler that can
cope with 1.5 bytecode in either C or C++, and then alter the OpenJDK
build system to use it :)

Basically you need to be able to build the OpenJDK langtools (written in Java
with 1.5 constructs), then run them (which needs a 1.5-capable Java VM).  Or
some equivalent.

> If it does not provide this, users should have a simple way to
> bootstrap it in Gentoo... Providing a simple script is sufficient.
>

Then feel free to write one as I said.

> Thanks,
> Alon.
>



-- 
Andrew :-)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8



  reply	other threads:[~2008-09-17 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 12:38 [gentoo-java] icedtea6 bootstrap Alon Bar-Lev
2008-09-14 20:38 ` Andrew John Hughes
2008-09-15  4:12   ` Alon Bar-Lev
2008-09-15  5:08     ` Alon Bar-Lev
2008-09-16 23:44       ` Andrew Cowie
2008-09-17 17:40         ` Andrew John Hughes
2008-09-17 18:19           ` Alon Bar-Lev
2008-09-17 22:01             ` Andrew John Hughes [this message]
2008-09-16  8:58     ` Andrew John Hughes
2008-09-15 11:35   ` Philipp Riegger
2008-09-15 11:42     ` Philipp Riegger

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=17c6771e0809171501l78109c61s567f2da7e07273f1@mail.gmail.com \
    --to=gnu_andrew@member.fsf.org \
    --cc=alon.barlev@gmail.com \
    --cc=andrew@operationaldynamics.com \
    --cc=gentoo-java@lists.gentoo.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