The issue here (and the reason why the rule is to run build in en_US) is
that the build would be error prone if we allow running builds in
locales other than US English. In the past, we had several build errors
related to this, e.g., 'date' command produced differently formatted
date string for each locale which resulted in build errors.
Naoto
On 10/4/13 9:42 AM, Magnus Ihse Bursie wrote:
I agree that the general rule is to build in an English environment.
Unfortunately, on Windows, it is not as trivial, nor often possible to get
tools to produce different output by setting a locale. It is not the case with
cl.exe, anyway. And in this case, Microsoft apparently does not provide the
English version to French users. Hence this fix.
/Magnus
4 okt 2013 kl. 18:18 skrev Naoto Sato <naoto.s...@oracle.com>:
Hi Magnus,
Well, it would work for Latin languages, but not for others, e.g., CJK. I
thought that the general rule was to run the build in English environment. I
would think that French CL.EXE would produce English version string on Windows
configured for en_US locale.
Naoto
On 10/4/13 6:12 AM, Magnus Ihse Bursie wrote:
Bug: https://bugs.openjdk.java.net/browse/JDK-8025933
In France, it's not possible to download the English version of Visual
Studio; hence CL.EXE presents itself as:
Compilateur d'optimisation Microsoft (R) 32 bits C/C++ version
16.00.30319.01 pour 80x86
instead of
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01
for 80x86
With a simple fix we can handle this in configure as well.
WebRev:
http://cr.openjdk.java.net/~ihse/JDK-8025933-configure-support-french-cl.exe/webrev.01
/Magnus
