unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Svante Signell <svante.signell@telia.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Need help with upstream vs Debian emacs-23.4 + emacs-24.1 build differences
Date: Thu, 05 Jul 2012 12:06:35 -0400	[thread overview]
Message-ID: <w6r4sqyyyc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <1341488866.13218.31.camel@s1499.it.kth.se> (Svante Signell's message of "Thu, 05 Jul 2012 13:47:46 +0200")

Svante Signell wrote:

> Still the buildds have problems building the Debian version. From the
> build logs one can see there are differences mainly due to the autoloads
> target. What is triggering that one, timestamps of files, anything else?

Generally speaking, yes; if the timestamp of a *.el file under lisp is
newer than that of the associated loaddef file, the latter will get
updated. Actually, "sometimes" md5sums are used rather than timestamp,
but in the diffs you showed it looked like timestamps. (Don't suppose
Emacs's md5 somehow behaves oddly for you?)

> cp -a should be the same, right?

Yes; AFAIK.

>> I think the problem lies in the loaddefs.el being regenerated by the
>> autoloads. My problem is that I don't know why it happens, compared to
>> the tarball.

AFAIK, it should only be timestamp/md5sum issues. Patching lisp files
will of course change their timestamp...

Can you find the minimum sequence starting from a normal tarfile that
causes the issue?

But, it looked to me like the loaddefs diff just showed the same
information being included twice? Is that right? I still think that
while that is incorrect, it should not be harmful in itself.



  reply	other threads:[~2012-07-05 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 23:09 Need help with upstream vs Debian emacs-23.4 build differences Svante Signell
2012-06-29  6:49 ` Andreas Schwab
2012-06-29  8:01   ` Svante Signell
2012-07-02  0:44     ` Glenn Morris
2012-07-02  4:30       ` Glenn Morris
2012-07-02 21:15         ` Svante Signell
2012-07-02 21:10       ` Svante Signell
2012-07-05 11:47         ` Need help with upstream vs Debian emacs-23.4 + emacs-24.1 " Svante Signell
2012-07-05 16:06           ` Glenn Morris [this message]
2012-07-01 20:58   ` Need help with upstream vs Debian emacs-23.4 " Svante Signell

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=w6r4sqyyyc.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.org \
    --cc=svante.signell@telia.com \
    /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).