Re: Encoding problem when building

2013-01-23 Thread Kelly O'Hair
t;>>>>>$ locale >>>>>> LANG=C >>>>>>LC_CTYPE="C" >>>>>>LC_NUMERIC="C" >>>>>>LC_TIME="C" >>>>>>LC_COLLATE="C" >>>>>

Re: Encoding problem when building

2013-01-17 Thread Frank Ding
getting into generated sources? That's what we need to find out. Removing "-encoding ascii" is probably not the right answer, and if it is, will require some debate. -kto On Dec 30, 2012, at 9:25 PM, Frank Ding wrote: Hi

Re: Encoding problem when building

2013-01-09 Thread Kelly O'Hair
t;>ascii chars only? >>>> >>>>Best regards, >>>>Frank >>>> >>>> >>>>On 1/1/2013 12:47 AM, Kelly O'Hair wrote: >>>> >>>>In the past, the "-encoding ascii

Re: Encoding problem when building

2013-01-07 Thread Frank Ding
"the same". But my question is, how are any locale specific characters getting into generated sources? That's what we need to find out. Removing "-encoding ascii" is probably not the right answer, and if it is, will require some debate. -kt

Re: Encoding problem when building

2013-01-07 Thread Kelly O'Hair
asons I can't completely list right now. But it is important >>that regardless of the locale, the bits created during the >>build should be the same for everyone. >>The definition of "same" might not be bit for bit, but by >>

Re: Encoding problem when building

2013-01-04 Thread Frank Ding
chance of measuring "the same". But my question is, how are any locale specific characters getting into generated sources? That's what we need to find out. Removing "-encoding ascii" is probably not the right answer, and if it is, will require som

Re: Encoding problem when building

2013-01-04 Thread Kelly O'Hair
I assume someone will file a bug on this? I kind of have my hands full with build-infra right now. -kto On Jan 4, 2013, at 2:02 AM, Alan Bateman wrote: > On 04/01/2013 05:29, Frank Ding wrote: >> Hi Kelly >> I investigated how local specific characters get into generated sources in >> corba m

Re: Encoding problem when building

2013-01-04 Thread Alan Bateman
On 04/01/2013 05:29, Frank Ding wrote: Hi Kelly I investigated how local specific characters get into generated sources in corba module. Those classes are generated by following command idlj c:/openjdk/dep/jdk1.7.0_02/bin/idlj -J-XX:-PrintVMOptions -J-XX:+UnlockDiagnosticVMOptions -J-XX:-Lo

Re: Encoding problem when building

2013-01-04 Thread Volker Simonis
>> potential differences we have a fighting >> chance of measuring "the same". >> >> But my question is, how are any locale specific characters getting into >> generated sources? That's what we need to find out. >> >> Removing "-encoding

Re: Encoding problem when building

2013-01-03 Thread Frank Ding
t;the same". But my question is, how are any locale specific characters getting into generated sources? That's what we need to find out. Removing "-encoding ascii" is probably not the right answer, and if it is, will require some debate. -kto On Dec 30, 2012, at 9:25 PM, Fra

Re: Encoding problem when building

2012-12-31 Thread Kelly O'Hair
ht answer, and if it is, will require some debate. -kto On Dec 30, 2012, at 9:25 PM, Frank Ding wrote: > Hi > I have an encoding problem when building openjdk 8 on my Windows 7. My > windows is Chinese environment but I exported LANG=C in cygwin bash before > building. Th

Encoding problem when building

2012-12-30 Thread Frank Ding
Hi I have an encoding problem when building openjdk 8 on my Windows 7. My windows is Chinese environment but I exported LANG=C in cygwin bash before building. The issue is that in module corba and jdk, some java classes are generated by program. They happen to contain Chinese characters