From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: emacs-devel@gnu.org
Subject: Re: Windows 28.1 install/zip has el newer than elc for some files?
Date: Thu, 21 Apr 2022 19:03:53 +0300 [thread overview]
Message-ID: <83k0biqv86.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoT8powvmYWH3j4rWDCZSMXeypfbJD-xb276wmRuQv_k3Q@mail.gmail.com> (message from Corwin Brust on Thu, 21 Apr 2022 10:55:35 -0500)
> From: Corwin Brust <corwin@bru.st>
> Date: Thu, 21 Apr 2022 10:55:35 -0500
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> In short, I have no idea how the modification dates are being changed.
> It seems to me that they aren't:
>
> corwi@Avalon MINGW64 /d/emacs-build
> $ unzip -lv install/upload/emacs-28.1.zip | grep xwidget.el
> 28927 Defl:X 7669 74% 2022-03-11 01:04 8d0d1e4b
> emacs-28.1/share/emacs/28.1/lisp/xwidget.el
> 25110 Defl:X 7180 71% 2022-04-03 07:16 3d3a8c8c
> emacs-28.1/share/emacs/28.1/lisp/xwidget.elc
That's not what I see in the zip file that was originally on the GNU
FTP site:
28927 04/04/2022 18:17 share/emacs/28.1/lisp/xwidget.el
25113 04/04/2022 18:17 share/emacs/28.1/lisp/xwidget.elc
> You will see from the below that I am using the source tarball for the
> new versions I've recently posted however I did find that I need to
> run make clean or otherwise no ELN files are produced (even when I
> tried specifying NATIVE_FULL_AOT=1 to make). I'm assuming this need
> to make clean and then run autogen.sh isn't expected. Would it make
> sense to create a bug report for this?
I don't understand. I build Emacs from the tarball, and didn't need
any "make clean" to have the *.eln files built as part of the build
process. (And how is this related to the issue at hand?)
next prev parent reply other threads:[~2022-04-21 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:20 Windows 28.1 install/zip has el newer than elc for some files? Joel Reicher
2022-04-19 21:14 ` Corwin Brust
2022-04-19 23:20 ` Corwin Brust
2022-04-20 2:33 ` Corwin Brust
2022-04-20 3:15 ` Joel Reicher
2022-04-20 6:27 ` Eli Zaretskii
2022-04-21 15:55 ` Corwin Brust
2022-04-21 16:03 ` Eli Zaretskii [this message]
2022-04-21 16:08 ` Corwin Brust
2022-04-21 18:34 ` Eli Zaretskii
2022-04-21 16:11 ` Corwin Brust
2022-04-21 17:06 ` Corwin Brust
2022-04-22 6:02 ` Corwin Brust
2022-04-21 18:36 ` Eli Zaretskii
2022-04-22 1:20 ` Corwin Brust
2022-04-22 5:26 ` Eli Zaretskii
2022-04-22 5:53 ` Corwin Brust
2022-04-22 6:18 ` Corwin Brust
2022-04-22 6:45 ` Eli Zaretskii
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=83k0biqv86.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-devel@gnu.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.
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).