From: Tassilo Horn <tsdh@gnu.org>
To: ding@gnus.org
Subject: autoloads only generated on every 2nd make
Date: Thu, 20 Nov 2014 08:20:16 +0100 [thread overview]
Message-ID: <87wq6qfidr.fsf@thinkpad-t440p.tsdh.org> (raw)
Hi all,
I use the Gnus git version which I updated daily with
cd gnus/
git pull && make
Since recently, when I start emacs I get the error
File error: Cannot open load file, no such file or directory,
gnus-load
and indeed, there's no gnus/lisp/gnus-load.el.
When I run make a second time, the autoloads are generated just fine.
With another make, gnus-load.el is deleted again but autoloads aren't
regenerated.
The problem is that gnus/lisp/Makefile's default "all total" target
requires the targets clean-some and gnus-load.el. When I do that on the
command line, I first get
% make clean-some gnus-load.el
rm -f *.elc gnus-load.el auto-autoloads.* custom-load.*
lispdir="/home/horn/share/emacs/site-lisp/gnus" srcdir=. emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-make-cus-load .
...
Generating autoloads for assistant.el...
...
Saving file /home/horn/Repos/el/gnus/lisp/gnus-load.el...
...
which is all fine. But when I do it again, I get
% make clean-some gnus-load.el
rm -f *.elc gnus-load.el auto-autoloads.* custom-load.*
make: 'gnus-load.el' is up to date.
Huh? How can gnus-load.el by up to date? You've just deleted it...
I can't see any changes in Gnus' Makefile.ins, so it might also be a
problem with GNU make itself. That has been updated to 4.1 on 6th
November which could be the beginning of the problem although I feel
that it started more recently than that...
Any ideas welcome!
Bye,
Tassilo
next reply other threads:[~2014-11-20 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 7:20 Tassilo Horn [this message]
2015-01-26 4:13 ` Lars Ingebrigtsen
2015-01-26 7:15 ` Tassilo Horn
2015-01-26 15:14 ` Tassilo Horn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wq6qfidr.fsf@thinkpad-t440p.tsdh.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).