|--==> "VK" == Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes:
VK> Took me quite a while to twig onto the fact that *BUFFER* was read-only
VK> because the underlying *FILE* was mode 644 but owned by 'root'.
VK> The *REAL* problem was the previous 'make install' back a few
VK> weeks ago did this:
So you're installing as 'root', wouldn't you expect that any files
created during the install to be owned by 'root'?
VK> (No files need saving)
VK> Loading /home/valdis/src/xemacs-21.5/lisp/auto-autoloads...
VK> Loading /home/valdis/src/xemacs-21.5/lisp/mule/auto-autoloads...
VK> Removing old or spurious .elcs in directory tree
`/home/valdis/src/xemacs-21.5/src/../lisp'...
VK> Removing out-of-date /home/valdis/src/xemacs-21.5/lisp/finder-inf.elc
VK> Removing old or spurious .elcs in directory tree
`/home/valdis/src/xemacs-21.5/src/../lisp'...done
VK> Recompiling updated .els in directory tree
`/home/valdis/src/xemacs-21.5/src/../lisp'...
VK> Compiling /home/valdis/src/xemacs-21.5/lisp/finder-inf.el...
VK> Wrote /home/valdis/src/xemacs-21.5/lisp/finder-inf.elc
VK> Recompiling updated .els in directory tree
`/home/valdis/src/xemacs-21.5/src/../lisp'...done
Are these files getting rebuilt unconditionally during 'make install'?
Is the test for "out-of-date, old or spurious" files not doing its job
properly?
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|