From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Konrad Podczeck <konrad.podczeck@univie.ac.at>,
70090-done@debbugs.gnu.org
Subject: bug#70090: Build failure
Date: Sat, 29 Jun 2024 22:53:20 -0700 [thread overview]
Message-ID: <CADwFkmmi8N0cbyhNwGW33xpwGH63pQTeZCzJFegFijjF6uRmBw@mail.gmail.com> (raw)
In-Reply-To: <8634r3qbhp.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Apr 2024 15:30:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
>> Date: Tue, 30 Apr 2024 13:44:47 +0200
>> Cc: 70090@debbugs.gnu.org
>>
>> This time I get a build failure with /laim/list.el
>>
>> Loading leim/leim-list.el (source)...
>> Error: error ("Invalid byte opcode: op=0, ptr=0")
>> cconv-make-interpreted-closure(nil ((progn (quail-defrule "ling2" 12295 nil t) (quail-defrule "wan2" 9675 nil
>> t))) (t) nil nil)
>> (function (lambda nil (progn (quail-defrule "ling2" 12295 nil t) (quail-defrule "wan2" 9675 nil t))))
>> (eval-after-load "quail/PY-b5" #'(lambda nil (progn (quail-defrule "ling2" 12295 nil t) (quail-defrule "wan2"
>> 9675 nil t))))
>> eval-buffer(#<buffer *load*> nil "leim/leim-list.el" nil t)
>> load-with-code-conversion("/Users/konradpodczeck/documents/emacs/lisp/leim/leim-list.el" "leim/leim-list.el" t
>> nil)
>> load("leim/leim-list.el" t)
>> load("loadup.el")
>>
>> Invalid byte opcode: op=0, ptr=0
>>
>> make[1]: *** [emacs.pdmp] Error 255
>> make: *** [src] Error 2
>
> Did you clean up your source tree, as I suggested previously? If not,
> please do. There should be no stale *.elc files, and no stale *.o
> files.
More information was requested, but none was given within 8 weeks, so I'm
closing this bug.
If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.
prev parent reply other threads:[~2024-06-30 5:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 14:50 bug#70090: Build failure Konrad Podczeck
2024-03-30 15:26 ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 16:38 ` Eli Zaretskii
2024-03-30 17:01 ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 16:38 ` Eli Zaretskii
2024-03-31 14:11 ` Konrad Podczeck
2024-03-31 14:27 ` Eli Zaretskii
2024-04-10 7:58 ` Konrad Podczeck
2024-04-10 11:22 ` Eli Zaretskii
2024-04-30 11:44 ` Konrad Podczeck
2024-04-30 12:30 ` Eli Zaretskii
2024-06-30 5:53 ` Stefan Kangas [this message]
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=CADwFkmmi8N0cbyhNwGW33xpwGH63pQTeZCzJFegFijjF6uRmBw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=70090-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=konrad.podczeck@univie.ac.at \
/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.