Gnus development mailing list
 help / color / mirror / Atom feed
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 08:15:56 +0100	[thread overview]
Message-ID: <87twze2es3.fsf@gnu.org> (raw)
In-Reply-To: <87bnlmji1j.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Mon, 26 Jan 2015 15:13:28 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>>   % 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...
>
> Huh.  That does seem odd.
>
>> 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...
>
> I'm not seeing this myself, and I don't really understand the autoconf
> stuff in depth...

This is still absolute reproducible here even with a complete fresh
checkout.  "make clean-some gnus-load.el" in gnus/lisp/ alternates
between

--8<---------------cut here---------------start------------->8---
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 .
Loading cus-dep...
Directory .
Generating cus-load.el...
Generating cus-load.el...done
lispdir="/home/horn/share/emacs/site-lisp/gnus" srcdir=. emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-make-auto-load .
lispdir="/home/horn/share/emacs/site-lisp/gnus" srcdir=. emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-make-load
Generating /home/horn/tmp/gnus/lisp/gnus-load.el...
Compiling /home/horn/tmp/gnus/lisp/gnus-load.el...
--8<---------------cut here---------------end--------------->8---

and

--8<---------------cut here---------------start------------->8---
rm -f *.elc gnus-load.el auto-autoloads.* custom-load.*
make: 'gnus-load.el' is up to date.
--8<---------------cut here---------------end--------------->8---

Oh, what works is if I rename the gnus-load.el target to gnus-load.elx.
It seems that my make version behaves differently than previous versions
when a target is named like a file...

I'll go investigating with the make guys.

Bye,
Tassilo



  reply	other threads:[~2015-01-26  7:15 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 [this message]
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=87twze2es3.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).