From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Error incrementally compiling Emacs
Date: Mon, 14 Nov 2022 00:35:21 +0100 [thread overview]
Message-ID: <8735amfmvk.fsf@gmail.com> (raw)
Hi all!
I'm trying to upgrade my Emacs. Being on Arch, I have a PKGBUILD script
from AUR (https://aur.archlinux.org/packages/emacs-git) to build the git
version. Issuing the compilation invokes the package build system, in
this case IIUC `make`, and all should be well. However, I have some
errors:
From stderr:
Source file ‘/home/alessandro/Downloads/AUR/emacs-git/src/emacs-git/lisp/emacs-lisp/cl-extra.el’ newer than byte-compiled file; using older file
Source file ‘/home/alessandro/Downloads/AUR/emacs-git/src/emacs-git/lisp/emacs-lisp/cl-extra.el’ newer than byte-compiled file; using older file
Source file ‘/home/alessandro/Downloads/AUR/emacs-git/src/emacs-git/lisp/emacs-lisp/cl-extra.el’ newer than byte-compiled file; using older file
Source file ‘/home/alessandro/Downloads/AUR/emacs-git/src/emacs-git/lisp/emacs-lisp/cl-extra.el’ newer than byte-compiled file; using older file
In toplevel form:
../../lisp/emacs-lisp/cconv.el:88:2: Error: Wrong type argument: stringp, (#<buffer *Compiler Output*>)
make[3]: *** [Makefile:322: ../../lisp/emacs-lisp/cconv.elc] Error 1
make[3]: *** Waiting for unfinished jobs....
Source file ‘/home/alessandro/Downloads/AUR/emacs-git/src/emacs-git/lisp/emacs-lisp/cl-extra.el’ newer than byte-compiled file; using older file
In toplevel form:
```
../../lisp/emacs-lisp/macroexp.el:31:2: Error: Wrong type argument: stringp, (#<buffer *Compiler Output*>)
make[3]: *** [Makefile:322: ../../lisp/emacs-lisp/macroexp.elc] Error 1
In toplevel form:
../../lisp/emacs-lisp/byte-opt.el:75:2: Error: Invalid function: (#<buffer *Compiler Output*>)
make[3]: *** [Makefile:322: ../../lisp/emacs-lisp/byte-opt.elc] Error 1
In toplevel form:
../../lisp/emacs-lisp/comp.el:206:2: Error: Invalid function: (#<buffer *Compiler Output*>)
make[3]: *** [Makefile:322: ../../lisp/emacs-lisp/comp.elc] Error 1
In toplevel form:
../../lisp/emacs-lisp/bytecomp.el:161:2: Error: Invalid function: (#<buffer *Compiler Output*>)
make[3]: *** [Makefile:322: ../../lisp/emacs-lisp/bytecomp.elc] Error 1
make[2]: *** [Makefile:915: bootstrap-emacs.pdmp] Error 2
make[1]: *** [Makefile:542: src] 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]: *** [Makefile:413: advice-on-failure] Error 2
make: *** [Makefile:370: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
```
However, if I tweaked the script correctly, this is already the build
with `V=1`. I can rebuild the entire thing with `make bootstrap`, and it
would probably fix the problem, but I'd lose the precompiled files.
Do you know what can be the issue? Is this the right place to ask? Do
you know what I can further investigate?
Thanks!
--
Alessandro Bertulli
next reply other threads:[~2022-11-13 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 23:35 Alessandro Bertulli [this message]
2022-11-14 0:50 ` Error incrementally compiling Emacs Po Lu
2022-11-14 11:56 ` Alessandro Bertulli
2022-11-15 10:00 ` Alessandro Bertulli
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=8735amfmvk.fsf@gmail.com \
--to=alessandro.bertulli96@gmail.com \
--cc=help-gnu-emacs@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.
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).