From: "Mattias Engdegård" <mattiase@acm.org>
To: 63288@debbugs.gnu.org
Cc: Brian Leung <leungbk@posteo.net>, Eli Zaretskii <eliz@gnu.org>,
Andrea Corallo <akrl@sdf.org>
Subject: bug#63288: 30.0.50; Emacs 30 packages fail to build with native comp on some machines
Date: Fri, 5 May 2023 16:12:14 +0200 [thread overview]
Message-ID: <098D461C-A742-45C4-BD85-B2F9B93F1D07@acm.org> (raw)
In-Reply-To: <83mt2jjqzg.fsf@gnu.org>
>> In https://github.com/nix-community/emacs-overlay/issues/318, we
>> received a report about failed external-package builds when using
>> Nix, which has some additional plumbing including
>> https://github.com/nixos/nixpkgs/blob/abcc3146aeb06b8d2ded75bddac3a63544a6be7e/pkgs/build-support/emacs/melpa2nix.el#L26-L32.
>>
>> It was observed that reverting
>> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=ea9831bb3cb4878273f6f848051c9b8c3c76d5f1
>> would resolve our issue.
>>
>> On my own machine, I don't always encounter the build failure (happened
>> to me once a few weeks ago, and then again today).
That's remarkable -- not only is it difficult to see anything wrong with that change (ea9831bb3c), it actually reverts byte-code generation for `ignore` forms in general so that the bytecode generated for `package-read-from-string` on master is again identical to that on emacs-29.
Andrea, does the native compiler somehow miscompile package-read-from-string?
Since the failure appears to be nondeterministic, perhaps there is a native-comp build race involved?
next prev parent reply other threads:[~2023-05-05 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 3:59 bug#63288: 30.0.50; Emacs 30 packages fail to build with native comp on some machines Brian Leung
2023-05-05 5:18 ` Eli Zaretskii
2023-05-05 14:12 ` Mattias Engdegård [this message]
2023-05-10 10:01 ` Andrea Corallo
2023-05-11 10:33 ` Mattias Engdegård
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=098D461C-A742-45C4-BD85-B2F9B93F1D07@acm.org \
--to=mattiase@acm.org \
--cc=63288@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=leungbk@posteo.net \
/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).