unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Intermitten build problems on Macos
Date: Thu, 11 Nov 2021 17:15:23 +0100	[thread overview]
Message-ID: <FC3217B9-8CCE-4FAE-B6B2-7D4AD0A367F0@gmail.com> (raw)
In-Reply-To: <875yt0oq5f.fsf@gnus.org>



> Am 10.11.2021 um 00:39 schrieb Lars Ingebrigtsen <larsi@gnus.org>:
> 
> Philipp <p.stephani2@gmail.com> writes:
> 
>> Yes, this happens to me all the time.  Deleting bootstrap-emacs also
>> fixes it temporarily.  The problem is generally that bootstrap-emacs
>> is occasionally not properly codesigned.  See e.g. this crash report:
> 
> Hm...   So is the problem that this bit doesn't always run?  Or...  is
> run at the wrong time?
> 
> temacs$(EXEEXT): $(LIBXMENU) $(ALLOBJS) $(LIBEGNU_ARCHIVE) $(EMACSRES) \
> [...]
> ifeq ($(DO_CODESIGN),yes)
> 	codesign -s - -f $@.tmp
> endif
> 
> Unfortunately, the Macos build doesn't fail for me now, so I can't test.
> I'll try to poke at this more the next time it fails.

I don't quite understand where the problem lies exactly.  The Makefile rule doesn't look wrong per se, but it does appear to result in binaries that are occasionally not codesigned.

Maybe it's worth investigating a more robust approach: Instead of having make-fingerprint modify the binary directly, have it write out the fingerprint into a generated C source file, then compile that and link it against the rest of the object files using the system linker.  That approach should be more portable, as it only relies on the system linker to produce correct binaries.


  parent reply	other threads:[~2021-11-11 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  5:21 Intermitten build problems on Macos Lars Ingebrigtsen
2021-11-09 10:37 ` Philipp
2021-11-09 23:39   ` Lars Ingebrigtsen
2021-11-10  1:34     ` Lars Ingebrigtsen
2021-11-11 16:15     ` Philipp [this message]
2021-11-12  3:05       ` Lars Ingebrigtsen
2021-11-09 12:45 ` Eli Zaretskii
2021-11-09 23:39   ` 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

  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=FC3217B9-8CCE-4FAE-B6B2-7D4AD0A367F0@gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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).