[m-dev.] opium-m and 0.9
Erwan Jahier
Erwan.Jahier at irisa.fr
Mon Dec 20 21:05:59 AEDT 1999
| while running configure:
|
| checking whether we can use sockets (for Opium-M)... yes
Thanks for spotting that.
--
Estimated hours taken: 0.2
Replace all occurrences of Opium-M by Morphine in The Mercury files.
configure.in:
trace/mercury_trace_external.c:
Replace Opium-M by Morphine.
Index: configure.in
===================================================================
RCS file: /home/mercury1/repository/mercury/configure.in,v
retrieving revision 1.197
diff -u -r1.197 configure.in
--- configure.in 1999/11/30 02:18:33 1.197
+++ configure.in 1999/12/20 09:57:33
@@ -2112,7 +2112,7 @@
#
# use TRY_LINK to see whether we can use sockets
#
-AC_MSG_CHECKING(whether we can use sockets (for Opium-M))
+AC_MSG_CHECKING(whether we can use sockets (for Morphine))
AC_CACHE_VAL(mercury_cv_sockets_work,
AC_TRY_LINK([
changequote(<<,>>)
Index: trace/mercury_trace_external.c
===================================================================
RCS file: /home/mercury1/repository/mercury/trace/mercury_trace_external.c,v
retrieving revision 1.33
diff -u -r1.33 mercury_trace_external.c
--- trace/mercury_trace_external.c 1999/12/10 04:24:08 1.33
+++ trace/mercury_trace_external.c 1999/12/20 10:04:46
@@ -286,7 +286,7 @@
/*
** We presume that the user's program has been invoked from
- ** within the debugger (e.g. Opium).
+ ** within the debugger (e.g. Morphine).
** The debugger (or the user) should set the
** MERCURY_DEBUGGER_UNIX_SOCKET or MERCURY_DEBUGGER_INET_SOCKET
** environment variable to tell the user's program which socket
--
R1.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions: mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------
More information about the developers
mailing list