The ALT_PARALLEL_COMPILE_JOBS=N is just for the native library builds
in the jdk repository, and it effectively just does a 'make -j N *.o'
which is safe, worked pretty well, and sped things up.
But it is only done on a per library basis.
The HOTSPOT_BUILD_JOBS=N is for hotspot only and I don't have many details
on this one, it's been around for a long time. As I understand it,
this is more of a top level 'make -j N'.
FYI...
The hotspot builds are much more cpu intensive than the jdk builds,
and hotspot builds behave more like a traditional C++ project.
But the jdk builds tend to be more disk intensive, many more files
involved and more bits created during a build.
When building the jdk, using local disk space or even /tmp will make
builds considerably faster.
-kto
Andrew John Hughes wrote:
2008/5/12 Andrew Haley <[EMAIL PROTECTED]>:
Kelly O'Hair wrote:
> We already use 'make -j' when building the .o files, and the dependencies
> should be ok for the .o files. So for native compilations I don't
> think we have a problem.
That's interesting; it certainly didn't used to work. I'll try again.
It didn't work with OpenJDK 6 this time last month. That's why I
added support for ALT_PARALLEL_COMPILE_JOBS and
HOTSPOT_BUILD_JOBS.
