summaryrefslogtreecommitdiffstats
path: root/bin/release
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2000-02-19 02:39:46 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2000-02-19 02:39:46 (GMT)
commit0f91b587f4a22afeb673af6882226c2d20ae96a6 (patch)
tree8def5b168b37cd63094283a6ff9e45a5731a73db /bin/release
parentfe91b80353da0dececa5a5891f994d37e3c8e67c (diff)
downloadhdf5-0f91b587f4a22afeb673af6882226c2d20ae96a6.zip
hdf5-0f91b587f4a22afeb673af6882226c2d20ae96a6.tar.gz
hdf5-0f91b587f4a22afeb673af6882226c2d20ae96a6.tar.bz2
[svn-r1979] Purpose:
Feature "improvement". Problem: The Makefile target triggers gmake to redo the whole auto-configure process if it sees any autoconfigure related files changed. It causes couple problems. One is that when multiple machines using --srcdir are running make, they may detect the changes and launch the autoconf at the same time. These end up as multiple hosts updating the same srcdir area together--bad things can happen. Another one is that when one modifies some Makefile.in, then try "make distclean" before launching the configure process. Instead of cleaning things, it started a configure, recreate all Makefiles and other files, then finally come around to do the distclean--who knows what it cleans by now since the Makefile is changed too. Last problem was that this auto-process will launch even for command "gmake -n ...". Solution: Renamed Makefile target to reconfigure so that the auto-checking is still available but must be launched explicitedly. If one wishes to have the auto-checking as default, one may do alias gmake "\gmake -i reconfigure; gmake \!* ".
Diffstat (limited to 'bin/release')
0 files changed, 0 insertions, 0 deletions