Hi All
Just update my Solaris to nv82 and nightly build fails:
"/net/bounty.prc.sun.com/j2se-jsn/max/work/myjdk/jdk/src/solaris/hpi/
native_threads/src/sys_api_td.c", line 101: syntax error before or
at: limit
"/net/bounty.prc.sun.com/j2se-jsn/max/work/myjdk/jdk/src/solaris/hpi/
native_threa
Hello Max,
Actually, we've already found this problem and passed to the team
responsible for the code (Cannot provide you bug id at the moment
though, but will do as soon as I get it). For now you can use following
workaround in openjdk sources (that worked for me):
--- src/solaris/hpi/
Alexey Ushakov wrote:
Hello Max,
Actually, we've already found this problem and passed to the team
responsible for the code (Cannot provide you bug id at the moment
though, but will do as soon as I get it). For now you can use following
workaround in openjdk sources (that worked for me):
Alexey Ushakov wrote:
Hello Max,
Actually, we've already found this problem and passed to the team
responsible for the code (Cannot provide you bug id at the moment
though, but will do as soon as I get it). For now you can use following
workaround in openjdk sources (that worked for me):
T
The bug was identified 8 weeks ago?
Anyway, this demonstrates that even us Sun employees don't have an
internal code repository for latest code fixes. :'(
Thanks all.
Max
On Feb 6, 2008, at 1:41 AM, Tim Bell wrote:
Alexey Ushakov wrote:
Hello Max,
Actually, we've already found this proble
Max (Weijun) Wang wrote:
The bug was identified 8 weeks ago?
Yes.
Anyway, this demonstrates that even us Sun employees don't have an
internal code repository for latest code fixes. :'(
Well - we do - I don't know offhand where Kelly's repo is, but I could dig it up in my email
archive. I
This is the change I did to JDK6 and the OpenJDK6 files.
Granted it's been pointed out that maybe just doing this include
on both Linux and Solaris should work, I wasn't sure about
doing this include on Linux at the time I made the change.
We use some pretty antique Linux systems for jdk5/jdk6 an
I agree that the more conservative fix you applied is perfect for
legacy releases.
For jdk7, we should forget about possible failure with antique Linux
releases, especially given this could only ever affect developers.
Martin
Kelly O'Hair wrote:
This is the change I did to JDK6 and the OpenJDK
Agreed. With jdk7, it's time to clean house where we can and take the risk.
-kto
Martin Buchholz wrote:
I agree that the more conservative fix you applied is perfect for
legacy releases.
For jdk7, we should forget about possible failure with antique Linux
releases, especially given this could
