Encoding problem when building

Alan Bateman Alan.Bateman at oracle.com
Fri Jan 4 10:02:40 UTC 2013

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:-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
>   Could you give me any hint about how to force idlj to generate ascii 
> chars only?
> Best regards,
> Frank
I don't know idlj but it may be using a FileWriter and therefore the 
default encoding.  As you path is "c:/openjdk" then I assume this must 
be Windows and cygwin, in which case you might (I'm not sure 100% sure) 
need to adjust it in the control panel. As a check, can you print the 
value of the file.encoding property in this environment.


More information about the build-dev mailing list