From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Pankaj Jangid <pankaj@codeisgreat.org>, 45605@debbugs.gnu.org
Subject: bug#45605: [macos] could not load dump file - more info
Date: Sat, 2 Jan 2021 18:28:08 +0000 [thread overview]
Message-ID: <X/C7OGZpsW+RrIcZ@breton.holly.idiocy.org> (raw)
In-Reply-To: <87zh1r6zvj.fsf@gnus.org>
On Sat, Jan 02, 2021 at 05:57:04PM +0100, Lars Ingebrigtsen wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > At this point all I can suggest is to make a fresh clone, run the
> > build there, collect the log of the entire build in a file, and post
> > here that file.
>
> I think I mentioned that I also got this exact same build failure on
> Macos, but that it went away with a "make bootstrap"? Pankaj hasn't
> said whether he's tried a bootstrap, though. (I think.)
I've had similar problems to this too, and sometimes all it takes is
to rerun make. I've no idea why it happens and I can't replicate it.
--
Alan Third
next prev parent reply other threads:[~2021-01-02 18:28 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 [this message]
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
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=X/C7OGZpsW+RrIcZ@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--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).