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: Fri, 22 Apr 2022 08:26:35 +0300 [thread overview]
Message-ID: <835yn1r8ms.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoS7Xd_2DRF6293wVSeDCqFYPQpExNVmfwtqcEokcJCP5Q@mail.gmail.com> (message from Corwin Brust on Thu, 21 Apr 2022 20:20:02 -0500)
> From: Corwin Brust <corwin@bru.st>
> Date: Thu, 21 Apr 2022 20:20:02 -0500
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> On Thu, Apr 21, 2022 at 1:36 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Which commands do you use to build the tarball?
>
> ./configure --with-modules --without-dbus --with-native-compilation
> --without-compress-install CFLAGS=-O2
>
> make install-strip -j 20 prefix=/d/emacs-build/install/emacs-28.1
>
> > Anything different from "./configure" followed by "make"?
>
> No, notwithstanding running makensis (after configure and make have
> run successfully).
I'm not familiar with makensis, but other than that, the only
explanation of the problem with timestamps can be some tool you use
under the hood, like if (for example) 'cp' or 'install' or 'tar' or
'gzip' don't preserve time stamps (which would mean they are buggy).
next prev parent reply other threads:[~2022-04-22 5:26 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
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 [this message]
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=835yn1r8ms.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).