From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: autoloads only generated on every 2nd make
Date: Mon, 26 Jan 2015 16:14:10 +0100 [thread overview]
Message-ID: <87oapl1sn1.fsf@gnu.org> (raw)
In-Reply-To: <87twze2es3.fsf@gnu.org> (Tassilo Horn's message of "Mon, 26 Jan 2015 08:15:56 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> I'll go investigating with the make guys.
Ok, the problem was that make uses a file cache which does not get
updated if a recipe deletes files that have nothing to do with the
target. Thus with "make clean-some gnus-load.el" make's cache still
thinks gnus-load.el exists and is up-to-date if it has been so before
clean-some.
I've committed a fix which uses recursive make calls for the
gnus-load.el target so that this is always executed with a file cache
reflecting the actual situation on the file system [1].
Bye,
Tassilo
[1] Oh, and sorry for the second commit completing the ChangeLog entry
and the non-ChangeLog formatted commit message in the first commit.
prev parent reply other threads:[~2015-01-26 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 7:20 Tassilo Horn
2015-01-26 4:13 ` Lars Ingebrigtsen
2015-01-26 7:15 ` Tassilo Horn
2015-01-26 15:14 ` Tassilo Horn [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oapl1sn1.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=larsi@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).