From: Glenn Morris <rgm@gnu.org>
To: 16020-done@debbugs.gnu.org
Subject: bug#16020: 24.3.50; wisent asks questions during build
Date: Sun, 01 Dec 2013 20:19:53 -0500 [thread overview]
Message-ID: <kx61r8uk06.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <3842F65D-A68C-4C59-AA6A-9A2F34204FEF@swipnet.se> ("Jan Djärv"'s message of "Sun, 1 Dec 2013 18:39:56 +0100")
Jan Djärv wrote:
> Ok, I thought the build system took care of that, i.e. recompiled all
> elc files.
It does recompile them all, eventually, but not necessarily in time for
them to be used, since we don't have dependency tracking for lisp files.
That's why `make bootstrap' deletes all .elc files first. So you won't
have these issues if you bootstrap.
prev parent reply other threads:[~2013-12-02 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 9:28 bug#16020: 24.3.50; wisent asks questions during build Jan Djärv
2013-12-01 9:49 ` Jan Djärv
2013-12-01 17:21 ` Glenn Morris
2013-12-01 17:39 ` Jan Djärv
2013-12-02 1:19 ` Glenn Morris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kx61r8uk06.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16020-done@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).