Yoshiaki Kasahara <kasahara(a)nc.kyushu-u.ac.jp> writes:
When I do 'make install' in the top directory,
'@lockdir@' is created
in the current dir. I believe 'lockdir' had been removed from
configure several months ago, but Makefile.in still contains several
lockdir-related codes. @lockdir@ won't substituted, so '@lockdir@' is
created in the current directory.
Thanks for the report. This patch fixes it.
2000-10-23 Yoshiki Hayashi <yoshiki(a)xemacs.org>
* Makefile.in.in: Remove lockdir related things.
Index: Makefile.in.in
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/Attic/Makefile.in.in,v
retrieving revision 1.1.2.26
diff -u -r1.1.2.26 Makefile.in.in
--- Makefile.in.in 2000/09/01 14:02:31 1.1.2.26
+++ Makefile.in.in 2000/10/23 10:02:32
@@ -123,7 +123,6 @@
## Where to install and expect the files that XEmacs modifies as it runs.
## These files are all architecture-independent. Right now, the
## only such data is the locking directory;
-## ${lockdir} is a subdirectory of this.
statedir=@statedir@
## Where to install and expect executable files to be run by XEmacs
@@ -199,11 +198,6 @@
## at once.
etcdir=@etcdir@
-## Where to create and expect the locking directory, where
-## the XEmacs locking code keeps track of which files are
-## currently being edited.
-lockdir=@lockdir@
-
## Where to put the DOC file.
docdir=@docdir@
@@ -520,10 +514,9 @@
## (e.g. /usr/local/lib/${PROGNAME}-20.5/sparc-sun-solaris2.6), we use
## make-path instead of mkdir. Not all mkdirs have the `-p' flag.
mkdir: FRC.mkdir
- ${MAKEPATH} ${COPYDESTS} ${lockdir} ${docdir} ${infodir} ${archlibdir} \
+ ${MAKEPATH} ${COPYDESTS} ${docdir} ${infodir} ${archlibdir} \
${mandir} ${bindir} ${datadir} ${libdir} ${pkgdir} \
${sitelispdir} ${moduledir} ${sitemoduledir}
- -chmod 0777 ${lockdir}
## Delete all the installed files that the `install' target would
## create (but not the noninstalled files such as `make all' would
--
Yoshiki Hayashi