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: Mon, 08 May 2006 19:24:40 -0500 [thread overview]
Message-ID: <445FE148.5060502@gentoo.org> (raw)
In-Reply-To: <445FC6EB.3080705@seznam.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Caster wrote:
> Uwe Klosa wrote:
>> Joshua Nichols wrote:
>>> Uwe Klosa wrote:
>>>>> Hi
>>>>>
>>>>> I've been using the migration overlay for about two weeks now and there haven't been any problems. I observed only one thing with the
>>>>> emerge of ant-1.6.5. When jdk-1.4 and jdk-1.5 are installed with 1.4 being the system vm the emerge of ant used 1.5 for compilation. I
>>>>> got ridd of that by removing 1.5. I don't know if this is a known issue or if it was only on my system where I had been using 1.5 as
>>>>> the system vm for quite some time. But this problem occured after migrating to the migration overlay and fixing all 1.5 issues.
>
> Same here, sun-jdk-1.4 set as system vm both for generation 1 and 2.
>
> # emerge -1 ant-core
> Calculating dependencies... done!
>>>> Emerging (1 of 1) dev-java/ant-core-1.6.5-r13 to /
>>>> checking ebuild checksums ;-)
>>>> checking auxfile checksums ;-)
>>>> checking miscfile checksums ;-)
>>>> checking apache-ant-1.6.5-src.tar.bz2 ;-)
> * Using: sun-jdk-1.5
>>>> Unpacking source...
> <ctrl+c>
>
>>> Are you positive that you were using a 1.4 JDK for the system vm of
>>> generation 1? java-check-environment _should_ be checking for this, and
>>> warning you about i. If that's not the case, I'd be interested to see if
>>> you could replicate that behavior, because I certainly haven't had this
>>> problem.
>>>
>
> I'm positive, java-check-environment reports no problem.
>
> BTW I thought the new system was to allow 1.5 jdk to be used for builds
> that are known to support it. Maybe it's the case of ant-core?
>
> Caster
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEX+FI8ATTzZyw6sMRAs1oAJ9s2Cc5X4fdXIx1kzi7yoYAhrpESgCeOEGY
Ed69lXH8wKXwixCJS23I5m8=
=of92
-----END PGP SIGNATURE-----
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-09 0:24 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 [this message]
2006-05-09 11:00 ` Caster
2006-05-09 12:44 ` Joshua Nichols
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=445FE148.5060502@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