bug#70090: Build failure

bug#70090: Build failure

[Konrad Podczeck]

With the code from today, 15.30, building Emacs failed, with the following error message:


Undefined symbols for architecture arm64:
  "_syms_of_json", referenced from:
      _main in emacs.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [temacs] Error 1
make[2]: *** [src] Error 2
make[1]: *** [actual-bootstrap] Error 2
***
*** "make bootstrap" failed with exit status 2.

make[1]: *** [advice-on-failure] Error 2
make: *** [bootstrap] Error 2


Konrad Podczeck

bug#70090: Build failure

[David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Same error here:

   CCLD     temacs

/usr/bin/ld: emacs.o: in function `main':
/home/dponce/installs/emacs/src/emacs.c:2478: undefined reference to `syms_of_json'
collect2: error: ld returned 1 exit status
   make[3]: *** [Makefile:739: temacs] Error  1
   make[2]: *** [Makefile:554: src] Error  2
   make[1]: *** [Makefile:1293: actual-bootstrap] Error  2


It seems that the json.c file is no more compiled after this commit:

author	Mattias Engdegård <mattiase@acm.org>	2024-03-30 15:13:24 +0100
committer	Mattias Engdegård <mattiase@acm.org>	2024-03-30 15:19:56 +0100
commit	1135ce461d188869e0294af45641edc2cbfacbf0 (patch)
tree	fe0c7ec4113ac62c6ab0d28b9bc8bc81dc005906
parent	890edfd2bb8fd79730919972cc82811b73c7f572 (diff)
download	emacs-1135ce461d188869e0294af45641edc2cbfacbf0.tar.gz
Always enable native JSON support and remove Jansson referencesHEADmaster
* src/json.c (Fjson__available_p): Remove.
* lisp/subr.el (json-available-p): Always return t.
* admin/nt/dist-build/build-dep-zips.py:
* configure.ac:
* doc/lispref/text.texi (Parsing JSON):
* java/INSTALL:
* java/org/gnu/emacs/EmacsNative.java (EmacsNative):
* lisp/term/w32-win.el (dynamic-library-alist):
* m4/ndk-build.m4 (ndk_INIT):
* msdos/sed1v2.inp:
* nt/INSTALL:
* nt/INSTALL.W64:
* src/Makefile.in:
* src/emacs.c (main):
* src/lisp.h:
Remove JSON configuration options and references to it and Jansson from
documentation and build files.
* etc/NEWS: Announce.

bug#70090: Build failure

[Eli Zaretskii]

> Date: Sat, 30 Mar 2024 16:26:28 +0100
> From:  David Ponce via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Same error here:
> 
>    CCLD     temacs
> 
> /usr/bin/ld: emacs.o: in function `main':
> /home/dponce/installs/emacs/src/emacs.c:2478: undefined reference to `syms_of_json'
> collect2: error: ld returned 1 exit status

Same response.

bug#70090: Build failure

[David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors]

On 30/03/2024 17:38, Eli Zaretskii wrote:
>> Date: Sat, 30 Mar 2024 16:26:28 +0100
>> From:  David Ponce via "Bug reports for GNU Emacs,
>>   the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Same error here:
>>
>>     CCLD     temacs
>>
>> /usr/bin/ld: emacs.o: in function `main':
>> /home/dponce/installs/emacs/src/emacs.c:2478: undefined reference to `syms_of_json'
>> collect2: error: ld returned 1 exit status
> 
> Same response.

I confirm the build is fixed.
Thanks!

bug#70090: Build failure

[Eli Zaretskii]

> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
> Date: Sat, 30 Mar 2024 15:50:23 +0100
> 
> With the code from today, 15.30, building Emacs failed, with the following error message:
> 
> 
> Undefined symbols for architecture arm64:
>   "_syms_of_json", referenced from:
>       _main in emacs.o
> ld: symbol(s) not found for architecture arm64
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[3]: *** [temacs] Error 1
> make[2]: *** [src] Error 2
> make[1]: *** [actual-bootstrap] Error 2
> ***
> *** "make bootstrap" failed with exit status 2.
> 
> make[1]: *** [advice-on-failure] Error 2
> make: *** [bootstrap] Error 2

Please try again, I hope I fixed this.

bug#70090: Build failure

[Konrad Podczeck]

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

Now I get a build failure with leim:

Loading leim/leim-list.el (source)...

Error: error ("Invalid byte opcode: op=0, ptr=0")
  cconv-make-interpreted-closure((lambda nil (progn (quail-defrule "ling2" 12295 nil t) (quail-defrule "wan2" 9675 nil t))) (t))
  (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 30.03.2024 um 17:38 schrieb Eli Zaretskii <eliz@gnu.org>:
> 
>> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
>> Date: Sat, 30 Mar 2024 15:50:23 +0100
>> 
>> With the code from today, 15.30, building Emacs failed, with the following error message:
>> 
>> 
>> Undefined symbols for architecture arm64:
>>  "_syms_of_json", referenced from:
>>      _main in emacs.o
>> ld: symbol(s) not found for architecture arm64
>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>> make[3]: *** [temacs] Error 1
>> make[2]: *** [src] Error 2
>> make[1]: *** [actual-bootstrap] Error 2
>> ***
>> *** "make bootstrap" failed with exit status 2.
>> 
>> make[1]: *** [advice-on-failure] Error 2
>> make: *** [bootstrap] Error 2
> 
> Please try again, I hope I fixed this.


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

bug#70090: Build failure

[Eli Zaretskii]

> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
> Date: Sun, 31 Mar 2024 16:11:21 +0200
> Cc: 70090@debbugs.gnu.org
> 
> Now I get a build failure with leim:
> 
> Loading leim/leim-list.el (source)...
> 
> Error: error ("Invalid byte opcode: op=0, ptr=0")
> 
>   cconv-make-interpreted-closure((lambda nil (progn (quail-defrule "ling2" 12295 nil t) (quail-defrule "wan2"
> 9675 nil t))) (t))
>   (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")

I suggest "make bootstrap".

bug#70090: Build failure

[Konrad Podczeck]

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")
make[3]: *** [emacs.pdmp] Error 255
make[2]: *** [src] Error 2
make[1]: *** [actual-bootstrap] Error 2
***
*** "make bootstrap" failed with exit status 2.
***
*** You could try to:
*** - run "make extraclean" and run "make" again (or, equivalently, run
***   "make bootstrap configure=default"), to rebuild Emacs with the
***   default configuration options, which might fix the problem
*** - run "git clean -fdx" and run "make bootstrap" again, which might
***   fix the problem if "make bootstrap configure=default" did not
***   !BEWARE! "git clean -fdx" deletes all files that are not under
***   !BEWARE! version control, which means that all changes to such
***   !BEWARE! files will be lost and cannot be restored later
*** - run "make V=1", which displays the full commands invoked by make,
***   to further investigate the problem
*** - report the problem and ask for help by sending an email to
***   bug-gnu-emacs@gnu.org, mentioning at least the build error
***   message, the platform, and the repository revision displayed by
***   "git rev-parse HEAD"
***
make[1]: *** [advice-on-failure] Error 

Konrad

bug#70090: Build failure

[Eli Zaretskii]

> 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.

bug#70090: Build failure

[Konrad Podczeck]

[-- 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 --]

bug#70090: Build failure

[Eli Zaretskii]

> 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.

bug#70090: Build failure

[Stefan Kangas]

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.