On 2013-07-26 21:13, Jonathan Gibbons wrote:
On 07/26/2013 11:58 AM, Tim Bell wrote:
Hi Jon:
Build folk,
I want to writing a script that loops over recent changesets, and
builds JDK each time. One factor to take into account is that I
will occasionally need to rerun the configure script.
Is it enough to see if (just) the generated-configure.sh has
changed? Or, do I need to check if any other files may have changed
as well
The generated-configure.sh files (there are two, one in open, one in
closed) are supposed to be regenerated and checked in whenever any of
the open/closed .m4 files are touched.
From time to time, we get OpenJDK fixes that involve the
common/autoconf/*.m4 files. In this case, even if the open
generated-configure.sh file is updated and checked in as per the
normal procedure, someone inside Oracle needs to step in and push an
update to the closed generated-configure.sh. The closed side of the
build will be broken until one of us does this. Yes, this is
unfortunate, but we do not have a better solution so far.
In summary, you should also look for updates to the .m4 files.
Tim
Thanks. Yes, in the end I simply checked the entire contents of the
autoconf directory.
This would be the best solution in my opinion as it also covers the spec
source files.
/Erik
--Jon
