public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Caster <cast3r@seznam.cz>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Re: How to predetermine if ebuilds will compile with 1.5?
Date: Mon, 05 Jun 2006 16:27:28 +0200	[thread overview]
Message-ID: <44843F50.4020706@seznam.cz> (raw)
In-Reply-To: <pan.2006.06.05.10.23.48.535333@comcast.net>

> Actually, what I was asking was _would_ it work without the overlay? I
> mean, if the ebuild is marked =virtual/jdk-1.4, then I could understand a
> potential for trouble. But when it's just marked (whether by laziness or
> whether it's correct) virtual/jdk, it'd be nice to know whether 1.5 could
> work.

No idea, how much the dependencies correspond with "would/wouldn't
work". I wouldn't bet on that. The question, why would you so
desperately try to have 1.5 JDK as (generation-1 without migration
overlay) system vm? It can only break things, and gain you nothing.
Somebody correct me if I'm wrong, but the bytecode compiled will be the
same no matter which JDK you use. Any optimisations are done with
run-time JIT compiling, and depends on the VM running the bytecode
(which can be different from the VM used to compile). So, without
migration overlay, you should best follow the java 1.5 faq, have 1.4 as
sytem vm and use whatever vm as user vm.

Caster
-- 
gentoo-java@gentoo.org mailing list



  parent reply	other threads:[~2006-06-05 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04 10:44 [gentoo-java] How to predetermine if ebuilds will compile with 1.5? Peter
2006-06-04 20:16 ` Caster
2006-06-05 10:23   ` [gentoo-java] " Peter
2006-06-05 14:15     ` Joshua Nichols
2006-06-05 14:27     ` Caster [this message]
2006-06-05 22:19       ` David Herron
2006-06-05 22:35         ` Wiktor Wandachowicz
2006-06-06  9:17         ` Caster
2006-06-06 13:35           ` David Herron
2006-06-08  7:07             ` Calvin Austin
2006-06-05 23:54       ` Greg Tassone

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=44843F50.4020706@seznam.cz \
    --to=cast3r@seznam.cz \
    --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