unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	larsi@gnus.org, 57309@debbugs.gnu.org
Subject: bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file"
Date: Mon, 22 Aug 2022 08:43:38 +0000	[thread overview]
Message-ID: <xjfbkscfz2d.fsf@ma.sdf.org> (raw)
In-Reply-To: <83k071dfsg.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Aug 2022 13:58:23 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: larsi@gnus.org,  57309@debbugs.gnu.org,  akrl@sdf.org
>> Date: Sun, 21 Aug 2022 12:45:05 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > I've removed src/emacs and src/bootstrap-emacs, and said "make".  That
>> > succeeded, but most of the preloaded files were loaded as *.elc.  Then
>> > I touch'ed every .el file that is preloaded, and said "make" again.
>> > This ELC+ELN-compiled all of them, and then successfully loaded and
>> > dumped them.
>> >
>> > Not sure what that means, but maybe try the same recipe?
>> 
>> That it succeeds is kind of what I'm afraid of :-).
>> 
>> I think Lars mentioned that a simple second make run made things work
>> for him, and now I'm afraid if I leave the debugger or touch anything, I
>> won't be able to reproduce the error again.
>> 
>> BTW, I think I've seen the same bug with the last change to Makefile.in,
>> only with a different error message "...incoherent something...", where
>> Lars mentioned he had seen that sort of error ca. once per month or so.
>> 
>> Something is really fishy here.
>
> The *.eln files aren't regenerated unless the corresponding *.el files
> are newer than their *.elc files.  This is a basic snafu we are living
> with since the development of Emacs 28, and it still isn't resolved.
> This happens even when Emacs changes in a way that requires a new
> subdirectory under native-lisp/, which is a clear sign that the *.eln
> files need to be regenerated.
>
> So yes, something is definitely "fishy".  I suspect that the changes
> Andrea did recently required a bump in the ABI_VERSION value, which
> would then prevent Emacs from trying to load the old *.eln files.  But
> maybe I'm missing something.  I hope Andrea chimes in soon.

Sorry for being late to the party, I'm back.  I don't think (or at least
so far I don't see why) my change should have required a new
ABI_VERSION.

I'm trying to read all this long thread searching for a recipe to
reproduce and understand better what is going on.

Thanks

   Andrea





  reply	other threads:[~2022-08-22  8:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 12:55 bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file" Gerd Möllmann
2022-08-20 13:07 ` Lars Ingebrigtsen
2022-08-20 13:12   ` Gerd Möllmann
2022-08-20 13:18   ` Lars Ingebrigtsen
2022-08-20 13:21     ` Gerd Möllmann
2022-08-20 13:26       ` Eli Zaretskii
2022-08-20 13:29         ` Lars Ingebrigtsen
2022-08-20 13:45           ` Eli Zaretskii
2022-08-21 11:55             ` Lars Ingebrigtsen
2022-08-20 13:27       ` Lars Ingebrigtsen
2022-08-20 13:37         ` Gerd Möllmann
2022-08-20 14:32           ` Gerd Möllmann
2022-08-20 15:08             ` Gerd Möllmann
2022-08-21  7:03               ` Gerd Möllmann
2022-08-21  8:50                 ` Gerd Möllmann
2022-08-21 10:13                   ` Eli Zaretskii
2022-08-21 10:45                     ` Gerd Möllmann
2022-08-21 10:58                       ` Eli Zaretskii
2022-08-22  8:43                         ` Andrea Corallo [this message]
2022-08-20 15:25             ` Eli Zaretskii
2022-08-21  6:39               ` Gerd Möllmann
2022-08-21  6:43                 ` Eli Zaretskii
2022-08-21  6:47                   ` Gerd Möllmann
2022-08-21  7:03                     ` Eli Zaretskii
2022-08-21  7:13                       ` Gerd Möllmann
2022-08-21 11:57           ` Lars Ingebrigtsen
2022-08-21 12:28             ` Gerd Möllmann
2022-08-21 12:36               ` Eli Zaretskii
2022-08-21 12:46                 ` Gerd Möllmann
2022-08-21 12:55                   ` Eli Zaretskii
2022-08-21 13:08                     ` Gerd Möllmann
2022-08-21 13:19                       ` Eli Zaretskii
2022-08-21 13:11                     ` Gerd Möllmann
2022-08-21 13:14                       ` Gerd Möllmann
2022-08-21 13:39                         ` Gerd Möllmann
2022-08-21 13:45                           ` Eli Zaretskii
2022-08-21 13:56                             ` Gerd Möllmann
2022-08-21 14:02                               ` Eli Zaretskii
2022-08-22  8:49                               ` Andrea Corallo
2022-08-22  8:56                                 ` Gerd Möllmann
2022-08-22  9:35                                   ` Andrea Corallo

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=xjfbkscfz2d.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=57309@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --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.
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).