| 1 |
Miroslav ©ulc wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I've faced a problem with migrated packages on my laptop. If I remember |
| 5 |
> well, I've read somewhere that the new Java system will always try to |
| 6 |
> build packages with the lower JDK possible. At least on my laptop (it's |
| 7 |
> a fresh install of Gentoo - I've installed it about two weeks ago) |
| 8 |
> packages are not built with the lowest JDK possible which results in |
| 9 |
> these bugs when compiling packages dependant on a badly built package: |
| 10 |
|
| 11 |
It's like this: |
| 12 |
|
| 13 |
DEPEND=">=virtual/jdk-1.4" will make it use 1.4 or higher JDK (it |
| 14 |
prefers the higher, you can tune that in |
| 15 |
/etc/java-config-2/build/jdk.conf) but it will rewrite the build.xml |
| 16 |
file(s) to -source 1.4 -target 1.4 so even with 1.5 JDK it should |
| 17 |
produce 1.4 compatible class files. |
| 18 |
|
| 19 |
DEPEND="=virtual/jdk-1.4" will use 1.4 JDK specifically, in case the |
| 20 |
package needs not just 1.4 language compliance but e.g. also breaks on |
| 21 |
1.4 -> 1.5 API changes or relies on something else that is specific only |
| 22 |
to 1.4. |
| 23 |
|
| 24 |
So seeing "Using: sun-jdk-1.5" is not a bug, note you also see the |
| 25 |
"Rewriting ./build.xml" that ensures proper -source and -target |
| 26 |
arguments. The problem could be if you have built something with 1.5 |
| 27 |
before the migration - run java-1.5-fixer to fix that. But it is also |
| 28 |
possible that the build.xml file(s) weren't properly rewritten, some |
| 29 |
were ommitted... and that would be a bug. You just need to find out |
| 30 |
which package is causing that (probably some that will want to be |
| 31 |
rebuilt with java-1.5-fixer over and over again). |
| 32 |
|
| 33 |
Caster |
| 34 |
-- |
| 35 |
gentoo-java@g.o mailing list |
Archives