1 |
O Mér, 12-04-2006 ás 12:21 +0000, Wiktor Wandachowicz escribiu: |
2 |
> Henrique Ferreiro <henrique.ferreiro@...> writes: |
3 |
> |
4 |
> > > # java-config-1 -L |
5 |
> > [sun-jdk-1.4.2.10] "Sun JDK |
6 |
> > 1.4.2.10" (/etc/env.d/java/20sun-jdk-1.4.2.10) * |
7 |
> |
8 |
> While the above is correct, the latter... |
9 |
> |
10 |
> > > # java-config-2 -L |
11 |
> > 1) Sun JDK 1.4.2.10 [sun-jdk-1.4] |
12 |
> > (/usr/share/java-config-2/vm/sun-jdk-1.4) |
13 |
> > *) Sun JDK 1.5.0.06 [sun-jdk-1.5] |
14 |
> > (/usr/share/java-config-2/vm/sun-jdk-1.5) |
15 |
> |
16 |
> ... explains a bit - you probably shouldn't have a SYSTEM JVM |
17 |
> set to Java 1.5 as of today. You can do so freely on your regular |
18 |
> user account. |
19 |
|
20 |
The the migration document shoud warm about this. Anyway, I did |
21 |
|
22 |
java-config-2 -S sun-jdk-1.4 |
23 |
|
24 |
Now: |
25 |
|
26 |
$ java -version |
27 |
java version "1.4.2_10" |
28 |
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03) |
29 |
Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode) |
30 |
|
31 |
But ant-core continues to build with java-1.5. |
32 |
> |
33 |
> > > # which java |
34 |
> > /usr/bin/java |
35 |
> > localhost ~ # ls -l /usr/bin/java |
36 |
> > lrwxrwxrwx 1 root root 22 Abr 6 17:00 /usr/bin/java |
37 |
> > -> /usr/bin/run-java-tool |
38 |
> > > # java -version |
39 |
> > java version "1.5.0_06" |
40 |
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) |
41 |
> > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) |
42 |
> |
43 |
> The above confirms that fact. |
44 |
> |
45 |
> > > # echo ${PATH} |
46 |
> > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin: |
47 |
> > /usr/i686-pc-linux-gnu/gcc-bin/3.4.6:/opt/sun-jdk-1.4.2.10/bin: |
48 |
> > /opt/sun-jdk-1.4.2.10/jre/bin:/opt/sun-jdk-1.4.2.10/jre/javaws |
49 |
> |
50 |
> Here the /usr/bin/java symliked to run-java-tool takes precedence |
51 |
> over the /opt/sun-jdk-1.4.2.10/bin (this is expected). |
52 |
> |
53 |
> > > # emerge -pv =sun-jdk-1.4* |
54 |
> > [ebuild NSF ] dev-java/java-sdk-docs-1.4.2 33,591 kB |
55 |
> > [ebuild Rf ] dev-java/sun-jdk-1.4.2.10-r13 USE="X alsa doc* |
56 |
> > nsplugin* -jce" 0 kB [5] |
57 |
> > |
58 |
> > Total size of downloads: 33,591 kB |
59 |
> > Portage overlays: |
60 |
> > [1] /usr/portage/local/layman/portage |
61 |
> > [2] /usr/portage/local/layman/bmg-main |
62 |
> > [3] /usr/portage/local/layman/gentopia |
63 |
> > [4] /usr/portage/local/layman/java-experimental |
64 |
> > [5] /usr/portage/local/layman/migration |
65 |
> |
66 |
> A nice set of overlays ;) |
67 |
> Most probably you've stepped onto a problem similar to the one already |
68 |
> discussed (mixing java-experimental and migration overlays is not always |
69 |
> healthy), see here: |
70 |
> http://thread.gmane.org/gmane.linux.gentoo.java/825/focus=825 |
71 |
> |
72 |
> However, setting your preferred gen-2 system VM and rebuilding the offensive |
73 |
> packages should help. You can try to find them by using: |
74 |
> |
75 |
> # emerge -pvet junit | less |
76 |
> |
77 |
> But spotting said packages requires a bit of patience and a good eye :) |
78 |
> However, the situation is fixable, either manually or maybe through |
79 |
> the java-1.5-fixer (http://article.gmane.org/gmane.linux.gentoo.java/839) |
80 |
> |
81 |
> BTW, if you choose to try the java-1.5-fixer script, could you please |
82 |
> describe your experiences? I never used this (never needed it, though) |
83 |
> but I'm curious how this could help in such situation. |
84 |
> |
85 |
> Wiktor |
86 |
> |
87 |
|
88 |
-- |
89 |
gentoo-java@g.o mailing list |