unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 54098@debbugs.gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: bug#54098: 29.0.50; Unexec build broken
Date: Tue, 22 Feb 2022 16:12:09 +0800	[thread overview]
Message-ID: <87a6ejb9ra.fsf@yahoo.com> (raw)
In-Reply-To: <87wnhnbcrk.fsf@yahoo.com> (Po Lu's message of "Tue, 22 Feb 2022 15:07:11 +0800")

Po Lu <luangruo@yahoo.com> writes:

> I get:
>
> In titdic-convert:
> international/titdic-cnv.el:473:2: Error: Attempt to modify read-only object: (generic dispatches-left methods)
> international/titdic-cnv.el:473:2: Error: Invalid function: "
> In titdic-convert:
> international/titdic-cnv.el:473:2: Error: Attempt to modify read-only object: (generic dispatches-left methods)"
> Makefile:328: recipe for target
> 'c:/emacs/emacs-29.0.50/lisp/international/titdic-cnv.elc' failed
>
> When trying to build an unexec build, where, presumably, some more
> things in pure space are read only.
>
> Thanks.

The problem is that `byte-run-strip-symbol-positions' can modify forms
which are in pure space.

It should return a copy of the form instead, but I don't know if the
rest of the byte compiler relies on the side effects symbol position
stripping.

Alan, WDYT?





  reply	other threads:[~2022-02-22  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wnhnbcrk.fsf.ref@yahoo.com>
2022-02-22  7:07 ` bug#54098: 29.0.50; Unexec build broken Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-22  8:12   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-22 11:15     ` Alan Mackenzie
2022-02-22 11:17       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23 21:23         ` Alan Mackenzie
2022-02-24  0:19           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-24 17:38             ` Alan Mackenzie

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=87a6ejb9ra.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54098@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=luangruo@yahoo.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 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).