From: Eli Zaretskii <eliz@gnu.org>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 70090@debbugs.gnu.org
Subject: bug#70090: Build failure
Date: Wed, 10 Apr 2024 14:22:35 +0300 [thread overview]
Message-ID: <8634rtwjgk.fsf@gnu.org> (raw)
In-Reply-To: <4E98B2FD-220D-469F-A4E1-FE7F0C6C6915@univie.ac.at> (message from Konrad Podczeck on Wed, 10 Apr 2024 09:58:59 +0200)
> 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.
next prev parent reply other threads:[~2024-04-10 11:22 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 [this message]
2024-04-30 11:44 ` Konrad Podczeck
2024-04-30 12:30 ` Eli Zaretskii
2024-06-30 5:53 ` Stefan Kangas
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=8634rtwjgk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70090@debbugs.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.