unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: alan@idiocy.org, larsi@gnus.org, 45605@debbugs.gnu.org
Subject: bug#45605: [macos] could not load dump file - more info
Date: Sun, 03 Jan 2021 17:01:36 +0200	[thread overview]
Message-ID: <83r1n2cbe7.fsf@gnu.org> (raw)
In-Reply-To: <m2czymlfzf.fsf@codeisgreat.org> (message from Pankaj Jangid on Sun, 03 Jan 2021 11:27:40 +0530)

> From: Pankaj Jangid <pankaj@codeisgreat.org>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  Eli Zaretskii <eliz@gnu.org>,
>   45605@debbugs.gnu.org
> Date: Sun, 03 Jan 2021 11:27:40 +0530
> 
> 1. If you notice at the beginning of ‘build_error.log’ the cleanup ‘rm’
> commands are missing; even though I used ‘make bootstrap’.

I suggest to find out what are the prerequisites for these commands,
and then try to understand why they don't always run.

> 2. To my surprise, ‘make -C ../admin/charsets all’ outputs “Nothing to
> be done” in case of successful build. I thought ‘make bootstraps’
> deletes everything and then starts configure/make.

This is expected: "make bootstrap" doesn't everything.  You need "make
extraclean" or somesuch to do that.

> 3. Same was the case with ‘make -C ../admin/grammers’ and a few other
> directories.

Likewise.

> 4. Lots of charset reloading seen in ‘build_error.log’. That did not
> happen in  ‘build_clean.log’.

Expected, because they existed before the build.

> 5. First ELC command, after emacs binary is built, produces
> error. Perhaps because the binary and pdmp fingerprint mismatch.

I suspect some problem related to src/macuvs.h and its generation
during the build.





  reply	other threads:[~2021-01-03 15:01 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 [this message]
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=83r1n2cbe7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45605@debbugs.gnu.org \
    --cc=alan@idiocy.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).