[m-rev.] for review: fix file creation order

[Zoltan Somogyi]

configure.in:
	Fix a bug I introduced when making most configure-created files
	nonexecutable: we created files in the script directory in the wrong
	order. The bug prevented a scratch workspace from being compiled in
	profiling grades, for example.

Zoltan.

Index: configure.in
===================================================================
RCS file: /home/mercury/mercury1/repository/mercury/configure.in,v
retrieving revision 1.498
diff -u -b -r1.498 configure.in
--- configure.in	9 Aug 2007 01:36:09 -0000	1.498
+++ configure.in	10 Aug 2007 09:18:53 -0000
@@ -4594,7 +4594,12 @@
 deep_profiler/DEEP_FLAGS
 '
 
-output_files="$executable_output_files $nonexecutable_output_files"
+# The order in which we output files matters, because in some cases, one of the
+# files we output (e.g. scripts/parse_ml_options.sh-subr) will be bodily
+# included in other files we output (e.g. scripts/ml, scripts/c2init etc).
+# If we attempted to create the latter files first, the bodily inclusion would
+# include the empty file instead.
+output_files="$nonexecutable_output_files $executable_output_files"
 
 # IMPORTANT NOTE
 # --------------
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------