all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70090@debbugs.gnu.org
Subject: bug#70090: Build failure
Date: Tue, 30 Apr 2024 13:44:47 +0200	[thread overview]
Message-ID: <A4E8CBE2-FA1C-4054-8FFB-93470DDAFB14@univie.ac.at> (raw)
In-Reply-To: <8634rtwjgk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]

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

> Am 10.04.2024 um 13:22 schrieb Eli Zaretskii <eliz@gnu.org>:
> 
>> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
>> Date: Wed, 10 Apr 2024 09:58:59 +0200
>> Cc: 70090@debbugs.gnu.org
>> 
>> With the code from today, 9.00 MEZ, I got the following error message, while trying to make a new build of Emacs 30:
>> 
>> 
>> In toplevel form:
>> cedet/semantic/wisent/python.el:30:11: Error: Symbol’s function definition is void: define-skeleton
>> make[3]: *** [cedet/semantic/wisent/python.elc] Error 1
>> make[2]: *** [compile-main] Error 2
>> make[1]: *** [lisp] Error 2
>> ***
>> *** "make all" failed with exit status 2.
>> ***
>> *** You could try to:
>> *** - run "make bootstrap", which might fix the problem
>> *** - run "make V=1", which displays the full commands invoked by make,
>> ***   to further investigate the problem
>> ***
>> make[1]: *** [advice-on-failure] Error 2
>> make: *** [all] Error 2
>> 
>> 
>> 
>> 
>> After doing "make bootstrap", the error maessage was as follows:
>> 
>> 
>> Error: error ("Eager macro-expansion failure: (error \"(require cl-lib) while preparing to dump\")")
>>  signal(error ("Eager macro-expansion failure: (error \"(require cl-lib) while preparing to dump\")"))
>>  error("Eager macro-expansion failure: %S" (error "(require cl-lib) while preparing to dump"))
>>  internal-macroexpand-for-load((eval-when-compile (require 'cl-lib)) nil)
>>  eval-buffer(#<buffer  *load*> nil "emacs-lisp/ring.el" nil t)
>>  load-with-code-conversion("/Users/konradpodczeck/Documents/emacs/lisp/emacs-lisp/ring.el" "emacs-lisp/ring.el" nil nil)
>>  load("emacs-lisp/ring")
>>  load("loadup.el")
>> Eager macro-expansion failure: (error "(require cl-lib) while preparing to dump")
> 
> I don't understand how you get that, since loadup.el doesn't load
> emacs-lisp/ring.  Maybe try cleaning up your source tree.


[-- Attachment #2: Type: text/html, Size: 12047 bytes --]

  reply	other threads:[~2024-04-30 11:44 UTC|newest]

Thread overview: 11+ 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 [this message]
2024-04-30 12:30             ` Eli Zaretskii

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=A4E8CBE2-FA1C-4054-8FFB-93470DDAFB14@univie.ac.at \
    --to=konrad.podczeck@univie.ac.at \
    --cc=70090@debbugs.gnu.org \
    --cc=eliz@gnu.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 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.