Hi Brian,
The "docs" are here:
http://openjdk.java.net/projects/build-infra/guide.html
with a small cheat-sheet at the end for some old v new options, but I
don't see everything eg docs/samples/demos. "configure --help" may also
show you what you need.
BTW I think debug and fastdebug are sk
Is there a list of "features" that can be turned on and off? With the
old build, I customize it with environment variables like
SKIP_FASTDEBUG_BUILD, NO_DOCS, NO_SAMPLES, and NO_DEMOS, which shaves
lots of time off the build. Are there equivalent configure flags for
these?
On 4/12/2012 5:47
Actually the long-standing recommended practice is to explicitly set
source, target, and encoding when compiling:
https://blogs.oracle.com/darcy/entry/build_advice_set_source_target
This means you get the language semantics you're asking for :-) This is
appropriate when building the JDK t
The filed that needed modifying turned out to be
jdk/makefiles/common/shared/Defs-java.gmk
It explicitly sets source and target versions. As you suggest this shouldn't be
necessary. I can see why specifying source/target is necessary for code
compiled with the bootstrap javac but in other cases
Hi,
when building parts of the JDK, mostly the presence of a C-compiler is asked and therefore required,
even if there are no C-sources to be compiled by this package. E.G. one can't build the
java.nio.charset package without a C-compiler installed. This is especially problematic on Windows,
b
Looks good!
2012/4/20 Magnus Ihse Bursie :
> In the build-infra hg repo, we allowed execute permission to be set on
> files, including common/bin/logger.sh, which is called by the Makefile.
>
> The official hg repos strip this bit, so when integrating to the build
> forest, this was lost, causing
Yes, a leftover exist in Setup.gmk thanks for spotting that David!
the -source 7 -target 7 should be replaced with $(BOOT_JDK_SOURCETARGET)
which is setup by configure and stored in the spec.gmk file.
That flag is only be used for compiling code that has to be
run by the boot jdk. The particular
On 2012-04-20 06:51, Mahesh Pujari wrote:
You are using ccache. It might be the case that a previous
compilation failed (due to out of disk space at that time?) and that
ccache stored away a bad result. That shouldn't really happen, but,
well... You can try to clear
In the build-infra hg repo, we allowed execute permission to be set on
files, including common/bin/logger.sh, which is called by the Makefile.
The official hg repos strip this bit, so when integrating to the build
forest, this was lost, causing the Makefile to fail since it can't
execute logge
