unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Pankaj Jangid <pankaj@codeisgreat.org>, 45605@debbugs.gnu.org
Subject: bug#45605: 28.0.50; [macos] could not load dump file
Date: Sun, 17 Apr 2022 16:10:31 +0200	[thread overview]
Message-ID: <87czhf3inc.fsf@gmail.com> (raw)
In-Reply-To: <878rs395hb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 17 Apr 2022 15:58:24 +0200")

>>>>> On Sun, 17 Apr 2022 15:58:24 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> Lars Ingebrigtsen <larsi@gnus.org> writes:
    >>> Binary is built. But in the end of ‘make bootstrap’, and when I run
    >>> the executable, I get this,
    >>> 
    >>> desired fingerprint:
    >>> a34ddd269ef1a8b036d7dc1d011d235ea4a6b4889bc78aa11ed1e593906e85d1
    >>> found fingerprint:
    >>> c309a34afb78f953a36914d34d5b85e140ac96638f85a8fbadd4ee287beb52d8
    >>> emacs: could not load dump file
    >>> "/Users/pankaj/work/code/savannah/emacs/src/emacs.pdmp": not built
    >>> for this Emacs executable
    >>> 
    >>> I built on HEAD -> master -> 0f561ee55348ff451600cc6027db5940ee14606f
    >> 
    >> I saw this again today (on Catalina) on a "git pull; make -j4
    >> bootstrap".  The next "make -j4 bootstrap" worked OK, though.

    Lars> This was a year ago, and I haven't seen this problem in a long while on
    Lars> Macos, so it might have been fixed in the meantime, I guess?

    Lars> Pankaj, are you still seeing this problem in recent Emacs versions?

I saw it on master earlier this week, but I was a naughty boy: I'd
C-c'd the build half way through because Iʼd forgotten to make a
change (and I donʼt use '-j', I like my mac not to crash).

Robert
-- 





  reply	other threads:[~2022-04-17 14:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02  3:06 bug#45605: 28.0.50; [macos] could not load dump file Pankaj Jangid
2021-01-02  4:38 ` Lars Ingebrigtsen
2021-01-02  6:58 ` Eli Zaretskii
2021-01-02  7:21   ` Pankaj Jangid
2021-01-02  7:28     ` Eli Zaretskii
2021-01-02  7:23   ` Pankaj Jangid
2021-01-02  7:36 ` bug#45605: [macos] could not load dump file - more info Pankaj Jangid
2021-01-02  8:04   ` Eli Zaretskii
2021-01-02 14:41     ` Pankaj Jangid
2021-01-02 14:50       ` Eli Zaretskii
2021-01-02 16:27         ` Pankaj Jangid
2021-01-02 16:41           ` Eli Zaretskii
2021-01-02 16:57             ` Lars Ingebrigtsen
2021-01-02 17:07               ` Eli Zaretskii
2021-01-02 18:28               ` Alan Third
2021-01-03  5:57                 ` Pankaj Jangid
2021-01-03 15:01                   ` Eli Zaretskii
2021-01-11 15:45 ` bug#45605: 28.0.50; [macos] could not load dump file Lars Ingebrigtsen
2022-04-17 13:58   ` Lars Ingebrigtsen
2022-04-17 14:10     ` Robert Pluim [this message]
2022-04-17 17:10     ` Pankaj Jangid

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=87czhf3inc.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=45605@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=pankaj@codeisgreat.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).