[m-rev.] For Review: Fix bug #53, lmc calls mkinit incorrectly in non-ssdb grades.

[Paul Bone]

For review by anyone.

Estimated hours taken: 0.5
Branches: main

Fix for bug #53.  lmc can now build deep profiling executables that are able
to write out their Deep.data file.  Unfortunately this change prevents lmc from
building ssdb executables.  This trade off is acceptable at this time.

tools/lmc.in:
	lmc no longer passes --init-file $WORKSPACE/ssdb/mer_ssdb.init to mmc.
	All executables built with lmc are no-longer required to be linked with
	ssdb, mdbcomp and browse libraries.

Index: tools/lmc.in
===================================================================
RCS file: /home/mercury/mercury1/repository/mercury/tools/lmc.in,v
retrieving revision 1.14
diff -u -u -r1.14 lmc.in
--- tools/lmc.in	20 Feb 2008 03:10:00 -0000	1.14
+++ tools/lmc.in	3 Apr 2008 22:42:07 -0000
@@ -104,10 +104,9 @@
 	--link-object $gclib \
 	-lm @TRACE_BASE_LIBS_SYSTEM@ @READLINE_LIBRARIES@"
 
-# XXX browser.init and mdbcomp.init might need to be included even if tracing
-# is disabled if ssdb uses code from the browser or mdbcomp libraries
+# ssdb.init is not included here because it breaks deep profiling programs
+# built with lmc.
 INIT_FLAGS="\
-	--init-file $WORKSPACE/ssdb/mer_ssdb.init \
 	--trace-init-file $WORKSPACE/browser/mer_browser.init \
 	--trace-init-file $WORKSPACE/mdbcomp/mer_mdbcomp.init \
 	--init-file $WORKSPACE/library/mer_std.init \

--------------------------------------------------------------------------
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
--------------------------------------------------------------------------