GNU bug report logs - #18766
25.0.50; eldoc (after commit fb9dbc05a3ca0b3e69afd5b061c84c3802086834)

Previous Next

Package: emacs;

Reported by: Dmitriy Igrishin <dmitigr <at> gmail.com>

Date: Sat, 18 Oct 2014 18:39:02 UTC

Severity: normal

Tags: notabug

Found in version 25.0.50

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ivan Shmakov <ivan <at> siamics.net>
To: 18766 <at> debbugs.gnu.org
Subject: bug#18766: 25.0.50; eldoc (after commit fb9dbc05a3ca0b3e69afd5b061c84c3802086834)
Date: Mon, 20 Oct 2014 20:14:51 +0000
>>>>> Dmitriy Igrishin <dmitigr <at> gmail.com> writes:

[…]

 > I keep source and build directories of Emacs separately.  (The build
 > directory is not a subdir of the source tree.)  And from time to time
 > I rebuild Emacs by invoking: make && sudo make install.  I've
 > "grepped" for "eldoc-documentation-function-default" in my *source*
 > tree and found *binary* matches.  (Probably, sometime I've invoke make
 > in the source directory.)

	JFTR, – the .elc files, produced by the byte compiler as part of
	the build process, are actually placed in the /source/
	directory.

	It doesn’t make much sense to me, but it’s how the Emacs build
	process currently works.  Personally, I work-around this issue
	with something like:

$ mkdir emacs-2014-10-20-build 
$ cd emacs-2014-10-20-build 
$ lndir ../emacs 
$ ./configure …

 > Thus, I am clean the source tree and rebuild Emacs.  The problem is
 > gone, so it is mea culpa, rather than bug.  Sorry!  But this is a
 > question.  Why "make install" invoked in the *build* directory after
 > updating the source tree messed up the installation?  Thanks!

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A




This bug report was last modified 10 years and 269 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.