1 |
I found the root of the problem. java-config-wrapper was installing |
2 |
/usr/bin/java-config. This is basically a wrapper, as the name suggests. |
3 |
java-config-1 was installing /usr/bin/java-config-1. This was the old |
4 |
school java-config. java-config-2 was installing /usr/bin/java-config-2 |
5 |
.... AND installing the same thing to /usr/bin/java-config. A bit of an |
6 |
oversight on my part, so my apologies for the inconvenience. |
7 |
|
8 |
To fix this, I've bumped to java-config-2.0.22 and |
9 |
java-config-wrapper-0.8-r2. Please update to these versions. I can't |
10 |
stress how important it is keep everything in the overlay up to date, |
11 |
because packages will be bumped as bugs are found and fixed. |
12 |
|
13 |
Regardes, |
14 |
|
15 |
Josh |
16 |
|
17 |
Mathew Robertson wrote: |
18 |
> I was also having similar problems yesterday, as I had just done a |
19 |
> system update. re-emerging the java-config-wrapper has solved most of |
20 |
> them - thanks for the tip. |
21 |
> |
22 |
> Mathew Robertson |
23 |
> |
24 |
> Joshua Nichols wrote: |
25 |
>> Ivan Yosifov wrote: |
26 |
>>> Am Donnerstag, 20. April 2006 19:03 schrieb Ivan Yosifov: |
27 |
>>> |
28 |
>>>> Am Mittwoch, 19. April 2006 18:15 schrieb Joshua Nichols: |
29 |
>>>> |
30 |
>>>>> Ivan Yosifov wrote: |
31 |
>>>>> |
32 |
>>>>>> Am Dienstag, 18. April 2006 19:36 schrieb Joshua Nichols: |
33 |
>>>>>> |
34 |
>>>>>>> Ivan Yosifov wrote: |
35 |
>>>>>>> |
36 |
>>>>>>>> Hello, |
37 |
>>>>>>>> |
38 |
>>>>>>>> Happens while emergeing eclipse: |
39 |
>>>>>>>> |
40 |
>>>>>>>> home ~ # emerge -1 eclipse-sdk |
41 |
>>>>>>>> Calculating dependencies... done! |
42 |
>>>>>>>> |
43 |
>>>>>>>> |
44 |
>>>>>>>>>>> Emerging (1 of 1) dev-util/eclipse-sdk-3.1.2 to / |
45 |
>>>>>>>>>>> checksums files .... |
46 |
>>>>>>>>>>> checksums src_uri ;-) eclipse-sourceBuild-srcIncluded-3.1.2.zip |
47 |
>>>>>>>>>>> |
48 |
>>>>>>>> * Checking for sufficient physical RAM |
49 |
>>>>>>>> * Checking for bad CFLAGS |
50 |
>>>>>>>> * Found offending option -fomit-frame-pointer in your CFLAGS |
51 |
>>>>>>>> .... |
52 |
>>>>>>>> * Tip: use equery depgraph "=eclipse-sdk-3.1.2" to list all |
53 |
>>>>>>>> dependencies. |
54 |
>>>>>>>> |
55 |
>>>>>>>> /usr/local/portage/migration/migration/eclass/java-utils.eclass: |
56 |
>>>>>>>> line |
57 |
>>>>>>>> 97: [: -ge: unary operator expected |
58 |
>>>>>>>> Detected a JDK < 1.5.0 |
59 |
>>>>>>>> Detected a JDK >= 1.4.2 |
60 |
>>>>>>>> |
61 |
>>>>>>>> |
62 |
>>>>>>>>>>> Unpacking source... |
63 |
>>>>>>>>>>> |
64 |
>>>>>>>> /usr/local/portage/migration/migration/ is where I've put the |
65 |
>>>>>>>> migration overlay revision 2114. Bash is 3.1_p17. Is this an |
66 |
>>>>>>>> eclass |
67 |
>>>>>>>> bug or something else ? |
68 |
>>>>>>>> |
69 |
>>>>>>> Something else, I think. I've been working on the eclipse ebuilds |
70 |
>>>>>>> (while using migration-overlay, obviously), and hadn't noticed any |
71 |
>>>>>>> problems. |
72 |
>>>>>>> |
73 |
>>>>>>> It might have something to do with the ebuild itself. Someone |
74 |
>>>>>>> went and |
75 |
>>>>>>> committed a bump to 3.1.2 without consulting with us Java folks, so |
76 |
>>>>>>> I'm not sure what condition it is. Expect to see a new revision |
77 |
>>>>>>> in a |
78 |
>>>>>>> day or so... |
79 |
>>>>>>> |
80 |
>>>>>>> Josh |
81 |
>>>>>>> |
82 |
>>>>>> I am getting the same with the new eclipse-sdk-3.1.2-r1. I added |
83 |
>>>>>> some |
84 |
>>>>>> debugging output to the eclass in java-utils_is-vm-version-ge(): |
85 |
>>>>>> |
86 |
>>>>>> --- ./java-utils.eclass 2006-04-19 10:58:43.000000000 +0300 |
87 |
>>>>>> +++ /usr/local/portage/migration/migration/eclass/java-utils.eclass |
88 |
>>>>>> 2006-04-19 11:00:25.000000000 +0300 |
89 |
>>>>>> @@ -91,6 +91,12 @@ |
90 |
>>>>>> local vm_patch=$(echo ${vm_version} | cut -d. -f3) |
91 |
>>>>>> local vm_extra=$(echo ${vm_version} | cut -d. -f4) |
92 |
>>>>>> |
93 |
>>>>>> + echo ${vm_major} |
94 |
>>>>>> + echo ${vm_minor} |
95 |
>>>>>> + echo ${user_major} |
96 |
>>>>>> + echo ${user_minor} |
97 |
>>>>>> + echo ${vm_patch} |
98 |
>>>>>> + echo ${user_patch} |
99 |
>>>>>> if [ ${vm_major} -ge ${user_major} ] && [ ${vm_minor} -gt |
100 |
>>>>>> ${user_minor} ] ; then |
101 |
>>>>>> echo "Detected a JDK >= ${user_version}" |
102 |
>>>>>> return 0 |
103 |
>>>>>> |
104 |
>>>>>> and the output is: |
105 |
>>>>>> |
106 |
>>>>>> * Tip: use equery depgraph "=eclipse-sdk-3.1.2-r1" to list all |
107 |
>>>>>> dependencies. |
108 |
>>>>>> |
109 |
>>>>>> 1 |
110 |
>>>>>> 5 |
111 |
>>>>>> 1 |
112 |
>>>>>> 5 |
113 |
>>>>>> |
114 |
>>>>>> 0 |
115 |
>>>>>> /usr/local/portage/migration/migration/eclass/java-utils.eclass: |
116 |
>>>>>> line |
117 |
>>>>>> 103: [: -ge: unary operator expected |
118 |
>>>>>> Detected a JDK < 1.5.0 |
119 |
>>>>>> 1 |
120 |
>>>>>> 5 |
121 |
>>>>>> 1 |
122 |
>>>>>> 4 |
123 |
>>>>>> |
124 |
>>>>>> 2 |
125 |
>>>>>> Detected a JDK >= 1.4.2 |
126 |
>>>>>> |
127 |
>>>>>> |
128 |
>>>>>>>>> Unpacking source... |
129 |
>>>>>>>>> |
130 |
>>>>>> ,meaning that vm_patch is ending up empty and that seems to |
131 |
>>>>>> confuse -ge |
132 |
>>>>>> conditionals using it. |
133 |
>>>>>> |
134 |
>>>>> I'll have to look into this, but it probably just needs to sanity |
135 |
>>>>> checking for the vm_extra and company. |
136 |
>>>>> |
137 |
>>>>> Aside from that, what is the original of the ebuild for eclipse |
138 |
>>>>> that you |
139 |
>>>>> are using? Also, which VM are you using? I haven't been able to |
140 |
>>>>> quite |
141 |
>>>>> reproduce this problem... |
142 |
>>>>> |
143 |
>>>>> Josh |
144 |
>>>>> |
145 |
>>>> I am using the eclipse-sdk-3.1.2-r1 ebuild from the main tree, |
146 |
>>>> attached |
147 |
>>>> here for reference. I have sun-jdk 1.4.2.10-r13 and 1.5.0.06-r13 |
148 |
>>>> installed. |
149 |
>>>> The problem with vm_patch seems to be that |
150 |
>>>> |
151 |
>>>> java-config -f | sed -e "s/.*-\([0-9.]\+\).*/\1/" ( in |
152 |
>>>> java-utils_get-vm-version ) |
153 |
>>>> |
154 |
>>>> returns just "1.5" and so |
155 |
>>>> |
156 |
>>>> vm_patch=$(echo ${vm_version} | cut -d. -f3) ( in |
157 |
>>>> java-utils_is-vm-version-ge ) ends up being an empty string. There |
158 |
>>>> is no |
159 |
>>>> third field to cut. |
160 |
>>>> |
161 |
>>> |
162 |
>>> Still an issue with eclipse-sdk-3.1.2-r2 and migration overlay |
163 |
>>> revision 2129. |
164 |
>>> |
165 |
>>> |
166 |
>> |
167 |
>> Could you check the contents of /usr/bin/java-config ? If it is a |
168 |
>> python script, try remerging java-config-wrapper. |
169 |
>> |
170 |
>> I just finished helping a user in #gentoo-java that was having the |
171 |
>> same issue, and that did the trick. |
172 |
>> |
173 |
>> Now, I need to track down why it's the original java-config, instead |
174 |
>> of the new wrapper for java-config.... |
175 |
>> |
176 |
>> - Josh |
177 |
-- |
178 |
gentoo-java@g.o mailing list |