From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: Timestamps in ...-autoloads.el files Date: Wed, 11 May 2016 17:53:24 +0300 Message-ID: <8737pomysb.fsf@gmail.com> References: <87zize1mmq.fsf@gnu.org> <87si55h205.fsf@gmail.com> <87mvvde3h0.fsf@gnu.org> <87vba0mkwy.fsf@gmail.com> <87y4ew88km.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0VW2-00036C-82 for guix-devel@gnu.org; Wed, 11 May 2016 10:53:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b0VVw-0006Ts-2h for guix-devel@gnu.org; Wed, 11 May 2016 10:53:33 -0400 In-Reply-To: <87y4ew88km.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 21 Oct 2015 18:55:53 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel I've just noticed that our generated "=E2=80=A6-autoloads.el" files still h= ave unwished timestamps (SOURCE_DATE_EPOCH is not honored). To recap: we use "gnu/packages/patches/emacs-source-date-epoch.patch" to modify 'autoload-insert-section-header' function, and it should work, but it doesn't. IIUC this happens because "autoload.elc" file was compiled using the unpatched "autoload.el", but first things first. Try the following recipe in Emacs (installed with Guix): 1. M-: (setenv "SOURCE_DATE_EPOCH" "1") 2. Generate autoloads for any file with autoload cookies. If you don't have such a file at hand, make "/tmp/f1.el" file with this single line: ;;;###autoload(defun f1 nil) Then: "M-x update-file-autoloads " Now open "/tmp/auto1.el" and you'll see a "bad" timestamp like this one: (22323 17532 313464 85000). But! If you reevaluate 'autoload-insert-section-header' and try again the timestamp will be "good": 3. M-x find-function autoload-insert-section-header 4. Reevaluate it: C-M-x 5. M-x update-file-autoloads Now look at "/tmp/auto2.el": it contains (0 1 0 0) timestamp as expected. I looked at the compiled "autoload.elc" file and if I understood it correctly, it was compiled using the unpatched version of "autoload.el" (because there is no mention of SOURCE_DATE_EPOCH there). But I don't understand how it could happen since patching is performed before building. Any ideas? --=20 Alex