If the JDK 7 bug id of the change is provided, I can take a look at that
for back porting to OpenJDK 6.
-Joe
Kelly O'Hair wrote:
Phil has a point, I'm not sure how valid a jdk build is with a non-C
locale.
Using LANG=C is advised.
However, I have no objection to this change being made by someone.
The %b is a locale specific value and really should be avoided.
-kto
On Jan 3, 2011, at 9:31 AM, Phil Race wrote:
Whilst I don't know the specifics of this issue the Openjdk builds
require
that you use the 'C' psuedo-locale for builds and that the sanity check
will complain and point out that build failures are possible for
other locales.
So this would be "not a bug", or a bug in the 'date' program if its
ignoring
your locale setting of 'C'.
-phil.
On 12/31/2010 10:16 AM, Johnson Lau wrote:
Hi,
I've just found that OpenJDK 6 may stop builds on CP936 Mac & Linux.
Checked the latest repo and confirmed that the bug still exists.
http://hg.openjdk.java.net/jdk6/jdk6/jdk/file/3a8a8b5f1612/make/common/shared/Defs.gmk
Line #275
Currently, FULL_VERSION uses a format with local abbreviated month
name (%b).
On these platforms, date will produce a string in local language
with space
(i.e. [_1月] which indicates January),
which breaks the builds.
This is fixed in OpenJDK 7 already so I brought the patch into JDK 6.
Hope someone can merge this.
Thanks,
Johnson Lau
