From: Joshua Nichols <nichoj@gentoo.org>
To: Caster <cast3r@seznam.cz>
Cc: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Feedback on migration and experimental overlay
Date: Tue, 09 May 2006 07:44:59 -0500 [thread overview]
Message-ID: <44608ECB.1070904@gentoo.org> (raw)
In-Reply-To: <44607634.90607@seznam.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Caster wrote:
> Joshua Nichols wrote:
> > Ah... right. It's not a problem that 1.5 is being used to compile it.
>> The build.xml files get rewritten to make sure 1.4 bytecode gets compiled.
>>
>> By chance, have you configured anything in
>> /etc/java-config-2/build/compilers.conf ? By default, it should use the
>> lowest possible VM, but it can be configured more finely.
>>
>> Josh
>
> No, didn't change that. It has only the commented example line
> #COMPILERS="ecj-3.1 jikes javac"
> I don't see how to specify JDK version in there :)
I actually meant compilers.conf, not jdk.conf
> This is getting confusing, you have generation-1 system VM, generation-2
> system VM, this compilers.conf... Any docs that explain how all that
> works, what gets used where? :)
https://svn.gentooexperimental.org/svn/java/migration/docs/java-user.html
Generation-1 system vm is used by root, and conseuqnently for emerging
packages that are using the old eclasses, ie java-pkg (which would be
most everything at this point).
Generation-2 system vm is used for root.
Generation-2 build vm is configured by the jdk.conf, and is used for
emerging packages which use the new eclasses, ie java-pkg-2.
> And what means "Enabling generation-2 compatibility ..." line in some
> ebuilds? BTW those ebuilds then use jdk-1.4 while ant-core doesn't print
> this line and uses jdk-1.5...
That line is displayed when you have the stuff related to generation-2
installed, ie updated java-config, new vms etc. The new java-config
introduces /usr/bin/java, /usr/bin/jar, etc. These can read GENTOO_VM to
know what vm to be using, so we set that to make sure JAVA_HOME and
/usr/bin/java use the same vm.
>
> Seems ant-tasks is affected as well, and can't be built because of that.
> http://bugs.gentoo.org/show_bug.cgi?id=132764
>
Quite aware of the bug now. It didn't happen on the system I was testing
on, but now I'm hitting it as well.
> Caster
>
> P.S. Um why doesn't this list have reply-to header pointing to the list
> address...
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEYI7L8ATTzZyw6sMRAqRwAJ9+NB0LHmFQMSrYx6vYP8rUWpAIeACfQu4R
4k1CE9bqrSInmHsFHyrpfh0=
=f2mP
-----END PGP SIGNATURE-----
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-09 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 11:31 [gentoo-java] Feedback on migration and experimental overlay Uwe Klosa
2006-05-07 13:01 ` Joshua Nichols
2006-05-08 10:45 ` Uwe Klosa
2006-05-08 22:32 ` Caster
2006-05-09 0:24 ` Joshua Nichols
2006-05-09 11:00 ` Caster
2006-05-09 12:44 ` Joshua Nichols [this message]
2006-05-09 13:08 ` Caster
2006-05-09 16:49 ` [gentoo-java] eselect java broken? Caster
2006-05-09 17:30 ` Joshua Nichols
2006-05-09 17:32 ` Caster
2006-05-09 17:51 ` Joshua Nichols
2006-05-09 18:03 ` Caster
2006-05-10 13:05 ` Caster
2006-05-10 13:14 ` Joshua Nichols
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=44608ECB.1070904@gentoo.org \
--to=nichoj@gentoo.org \
--cc=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