A Windows tip:
* On Windows, I use:
make BUILD_LOG_WRAPPER= VERBOSE=
The logger tricks in the new makefiles seem to give Windows/CYGWIN grief,
not all the time
-kto
On Jul 9, 2012, at 3:12 PM, Kelly O'Hair wrote:
> The jdk8/build forest has been in sync for a
The current build-infra/jdk8 forest can now be configured using --enable-sjavac
This causes the build to do proper incremental builds of Java sources (all the
other
sources are already properly handled when building incrementally)
i.e. only the java sources that need to be compiled are actually c
Not sure I replied or not... This looks good to me.
-kto
On Jul 2, 2012, at 8:52 PM, Tim Bell wrote:
> All-
>
> This is the hotspot-only portion of the changes to allow building on Windows
> with any of MKS, Cygwin, or MinGW/MSYS as the 'Unix-like' shell environment:
>
> http://cr.openjdk.ja
Hello,
Please review the JDK8 changes for JEP 127: Improve Locale Data
Packaging and Adopt Unicode CLDR Data
(http://openjdk.java.net/jeps/127). The webrev is located at:
http://cr.openjdk.java.net/~naoto/6336885/webrev.00/
The main bug id for this enhancement is:
6336885: RFE: Locale Data
This isn't supposed to happen. At least it's the intention that
configure should avoid /usr/bin/link in favour of visual studio link.
VS10 in a different location is probably the reason for it.
What is the path to visual studio on this system? Is the environment
variable VS100COMNTOOLS to poin
after modifying the spec.gmk, the build is progressing.
Kumar
It looks like autoconf has messed up.
From the config.log
HOSTCC='C:/PROGRA~1/MSVS10/VC/BIN/cl.exe'
HOSTCXX='C:/PROGRA~1/MSVS10/VC/BIN/cl.exe'
HOSTLD='C:/devtools/cygwin/bin/link.exe'
It has picked cl.exe correctly, oopsie o
It looks like autoconf has messed up.
From the config.log
HOSTCC='C:/PROGRA~1/MSVS10/VC/BIN/cl.exe'
HOSTCXX='C:/PROGRA~1/MSVS10/VC/BIN/cl.exe'
HOSTLD='C:/devtools/cygwin/bin/link.exe'
It has picked cl.exe correctly, oopsie on link.exe.
Kumar
On 10/07/2012 10:59 AM, Kumar Srinivasan wrote:
The configure script does set a few variables in the spec.gmk file that is used
but the hotspot repo.
(It does read the spec.gmk file)
We did forget about STATIC_CXX though, it should be added to spec.gmk and set
appropriately,
then the hotspot makefile that looks at it should be adjusted, beca
