From: Alan Third <alan@idiocy.org>
To: Philipp <p.stephani2@gmail.com>
Cc: 45552@debbugs.gnu.org
Subject: bug#45552: 28.0.50; bootstrap-emacs apparently not correctly codesigned
Date: Tue, 31 Aug 2021 20:28:23 +0100 [thread overview]
Message-ID: <87mtoxfm7c.fsf@idiocy.org> (raw)
In-Reply-To: <m2czyr8mnd.fsf@MacBook-Pro.fritz.box> (Philipp's message of "Wed, 30 Dec 2020 14:10:46 +0100")
Philipp <p.stephani2@gmail.com> writes:
> The following happens for me (on macOS Big Sur on ARM 64, which needs
> codesigning) pretty frequently: every time Emacs needs to re-dump as
> part of `make', the code signature for bootstrap-emacs is somehow
> invalid. For example:
>
> $ ./config.status
> [...]
> $ gmake
> [...]
> /bin/sh: line 3: 18759 Killed: 9 EMACSLOADPATH= '../src/bootstrap-emacs' -batch --no-site-file --no-site-lisp -l autoload --eval "(setq generate-autoload-cookie \";;;###diary-autoload\")" --eval "(setq generated-autoload-file (expand-file-name (unmsys--file-name \"calendar/diary-loaddefs.el\")))" -f batch-update-autoloads ./calendar
> [...]
> $ src/bootstrap-emacs
> Killed: 9
>
> The crash reports for these crashes say
>
> Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
> Exception Codes: 0x0000000000000032, 0x0000000104098000
> Exception Note: EXC_CORPSE_NOTIFY
>
> Termination Reason: Namespace CODESIGNING, Code 0x2
>
> However, `codesign' thinks the signature is valid:
>
> $ codesign -v -v src/bootstrap-emacs
> src/bootstrap-emacs: valid on disk
> src/bootstrap-emacs: satisfies its Designated Requirement
>
> Removing src/bootstrap-emacs and running `gmake' again fixes the issue
> (until the next re-dump).
I think we fixed some problems around code signing recently. Is this
still an issue?
--
Alan Third
next prev parent reply other threads:[~2021-08-31 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 13:10 bug#45552: 28.0.50; bootstrap-emacs apparently not correctly codesigned Philipp
2021-08-31 19:28 ` Alan Third [this message]
2021-09-04 16:55 ` Philipp
2022-06-07 12:20 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtoxfm7c.fsf@idiocy.org \
--to=alan@idiocy.org \
--cc=45552@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.