For reason or reasons unknown (probably related to the old build
system), I had this in my environment:
_JAVA_OPTIONS=-Dfile.encoding=ASCII
This causes the shiny new build system's "java -version" to read the
java version as:
"Picked up _JAVA_OPTIONS: -Dfile.encoding=ASCII"
and fail ver
Fair enough. It was a bump between old and new build systems, just
wanted to note it.
-s
On 2/24/13 4:05 PM, David Holmes wrote:
On 24/02/2013 4:38 AM, Steven R. Loomis wrote:
For reason or reasons unknown (probably related to the old build
system), I had this in my environment
Omair,
I'm sorry I did not see this before. I probably would not have noticed
it except I happened to notice this reply.
I'm responsible for maintaining the version of ICU in JDK, and also
(read: main day job) IBM's lead for ICU for C/C++. ( But I speak for
myself here, of course. )
I t
6a329,330
> virtual void getKerningAdjustment(LEPoint &adjustment) const = 0;
On 6/24/13 5:24 p.m., Steven R. Loomis wrote:
Omair,
I'm sorry I did not see this before. I probably would not have
noticed it except I happened to notice this reply.
I'm responsible for m
Late to the party, but please note that the README-builds.html *still*
says that ccache is great and you should install it. Doesn't mention
*anything* about ccache being off by default or `--enable-ccache` being
needed. In fact, configure actively disables ccache if you use a
symlink to ccache fo
Filed: https://bugs.openjdk.java.net/browse/JDK-8065791
On 11/13/2014 10:59 PM, Steven R. Loomis wrote:
> Late to the party, but please note that the README-builds.html *still*
> says that ccache is great and you should install it. Doesn't mention
> *anything* about ccache being
