Check-in problem - was RE: [m-dev.] Installation + re-installatio n

[Ralph Becket]

I'm about to make the checkin below, but thanks to firewalls etc.
I have to do this from cygwin under Win2K.  Here's what I get:

$ cvs commit -F 2000-09-08.log .INSTALL.in
Use of uninitialized value at /home/mercury1/repository/CVSROOT/check.pl
line 18
4.
File `.INSTALL.in' appears to have no copyright message

Can't read from your terminal --- you appear to be using remote CVS.
You have no DISPLAY environment variable set so I don't know
how to interact with you.  Sorry.

Will not commit.

cvs server: Pre-commit check failed
cvs [server aborted]: correct above errors first!

Help!

Ralph


Estimated hours taken: 0.1

.INSTALL.in:
        Added explanatory comment concerning the behaviour
        of --prefix in configure and a note about setting
        the PATH env-var correctly when installing a new
        version of the compiler while you already have
        another installed.

Index: .INSTALL.in
===================================================================
RCS file: /home/mercury1/repository/mercury/.INSTALL.in,v
retrieving revision 1.5
diff -u -r1.5 .INSTALL.in
--- .INSTALL.in 1999/03/30 05:45:16     1.5
+++ .INSTALL.in 2000/09/08 09:12:54
@@ -23,6 +23,12 @@
 #         If you want the files to be installed someplace else,
 #         use the `--prefix <directory>' option to `configure'.
 #
+#      NOTE: If you use the `--prefix' option to configure,
+#      be aware that `mercury' is not automatically
+#      appended.  That is, `--prefix=/usr/local' will put
+#      files in /usr/local/bin, /usr/local/lib et cetera,
+#      *not* /usr/local/mercury/bin, /usr/local/mercury/lib.
+#
 #         The output from this stage will be automatically saved in the
 #         file `configure.log'.  Some debugging output is also saved to
 #         the file `config.log'.
@@ -32,6 +38,14 @@
 #
 #         The output from this stage will be automatically saved in the
 #         file `make.log'.
+#
+#      NOTE: If you have problems installing a new version
+#      of the compiler, you may find it helpful to either
+#      completely remove any existing versions of the
+#      compiler reachable on your PATH or, less drastically,
+#      alter your PATH variable so that any existing version
+#      of the mercury compiler is not accessible for the
+#      purposes of installing the new version.
 #
 # Step 3.  Run `make install'.
 #         This step will also take a long time.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------