Encoding problem when building

[Volker Simonis]

This is just a wild guess, but perhaps idlj uses the value of some
environment variables (or values derived from them - check
System.getProperties()) which contain non ASCII characters? This could be
something like PATH, HOSTNAME, USER. What exact characters are there in the
comment and what kind of comment is it? How does this comment look on a
"normal" system?

Regards,
Volker


On Fri, Jan 4, 2013 at 6:29 AM, Frank Ding <dingxmin at linux.vnet.ibm.com>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:-LogVMOutput -J-Xmx512m -J-Xms512m -J-XX:PermSize=32m
> -J-XX:MaxPermSize=160m -td "c:/openjdk/ojdk8_ojdk_739/../**
> ojdk8_ojdk_739-debug/corba/**gensrc" -i "../../../../src/share/**
> classes/org/omg/**PortableServer" -i "../../../../src/share/**
> classes/org/omg/**PortableInterceptor" -corba 3.0 -fall -pkgPrefix
> PortableServer org.omg ../../../../src/share/classes/**
> org/omg/PortableServer/poa.idl
>
>   I checked idlj help but there is no encoding specific option. My locale
> environment vars are listed below
>
> $ locale
> LANG=C
> LC_CTYPE="C"
> LC_NUMERIC="C"
> LC_TIME="C"
> LC_COLLATE="C"
> LC_MONETARY="C"
> LC_MESSAGES="C"
> LC_ALL=
>
>   Could you give me any hint about how to force idlj to generate ascii
> chars only?
>
> Best regards,
> Frank
>
>
> On 1/1/2013 12:47 AM, Kelly O'Hair wrote:
>
>> In the past, the "-encoding ascii" was important, all the reasons 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 minimizing the
>> 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 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
>>>   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 in comment.  However, they are compiled with explicit option
>>> "-encoding ascii" in makefile.  This results in unrecognizable chars
>>> complained by javac (Error: encoding ascii unmappable chars) .  I have a
>>> patch that removes all unnecessary "-encoding ascii" but I am not sure all
>>> its side effect.  Shall I submit a bug?
>>>
>>>   Best regards,
>>>   Frank
>>>
>>>
>