GNU bug report logs - #47161
28.0.50; [feature/native-comp] Failure to native-compile bytecomp.el etc.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47161 in the body.
You can then email your comments to 47161 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 28.0.50; [feature/native-comp] Failure to native-compile
 bytecomp.el etc.
Date: Mon, 15 Mar 2021 17:27:56 +0200

Suddenly manual native-compilation of some files fails.  Example:

  $ emacs -batch -l comp -f batch-byte-native-compile-for-bootstrap ../lisp/emacs-lisp/bytecomp.el
  Debugger entered--Lisp error: (wrong-type-argument "../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>)
    signal(wrong-type-argument ("../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>))
    comp--native-compile("../lisp/emacs-lisp/bytecomp.el")
    batch-native-compile()
    batch-byte-native-compile-for-bootstrap()
    command-line-1(("-l" "comp" "-f" "batch-byte-native-compile-for-bootstrap" "../lisp/emacs-lisp/bytecomp.el"))
    command-line()
    normal-top-level()

Am I doing something wrong?

In GNU Emacs 28.0.50 (build 40, i686-pc-mingw32)
 of 2021-03-15 built on HOME-C4E4A596F7
Repository revision: aabda4263bc2000a69e61e93a232e71f8afedec9
Repository branch: feature/native-comp
Windowing system distributor 'Microsoft Corp.', version 5.1.2600
System Description: Microsoft Windows XP Service Pack 3 (v5.1.0.2600)

Configured using:
 'configure -C --prefix=/d/usr --with-wide-int --with-native-compilation
 --enable-checking=yes,glyphs 'CFLAGS=-O0 -gdwarf-4 -g3''

Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
XPM ZLIB

Important settings:
  value of $LANG: ENU
  locale-coding-system: cp1255

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny dired dired-loaddefs
rfc822 mml mml-sec epa derived epg epg-config gnus-util rmail
rmail-loaddefs auth-source cl-seq eieio eieio-core cl-macs
eieio-loaddefs password-cache json map text-property-search time-date
subr-x seq byte-opt gv bytecomp byte-compile cconv mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loaddefs
cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils
iso-transl tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel dos-w32 ls-lisp disp-table term/w32-win w32-win
w32-vars term/common-win tool-bar dnd fontset image regexp-opt fringe
tabulated-list replace newcomment text-mode elisp-mode lisp-mode
prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-bar mouse jit-lock font-lock syntax facemenu
font-core term/tty-colors frame minibuffer cl-generic cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray
cl-preloaded nadvice button loaddefs faces cus-face macroexp files
window text-properties overlay sha1 md5 base64 format env code-pages
mule custom widget hashtable-print-readable backquote threads w32notify
w32 lcms2 multi-tty make-network-process nativecomp emacs)

Memory information:
((conses 16 73614 8612)
 (symbols 48 7803 0)
 (strings 16 22574 2563)
 (string-bytes 1 660985)
 (vectors 16 13350)
 (vector-slots 8 274690 9788)
 (floats 8 24 41)
 (intervals 40 263 110)
 (buffers 888 10))

Message #8 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Mon, 15 Mar 2021 15:48:01 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

> Suddenly manual native-compilation of some files fails.  Example:
>
>   $ emacs -batch -l comp -f batch-byte-native-compile-for-bootstrap ../lisp/emacs-lisp/bytecomp.el
>   Debugger entered--Lisp error: (wrong-type-argument "../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>)
>     signal(wrong-type-argument ("../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>))
>     comp--native-compile("../lisp/emacs-lisp/bytecomp.el")
>     batch-native-compile()
>     batch-byte-native-compile-for-bootstrap()
>     command-line-1(("-l" "comp" "-f" "batch-byte-native-compile-for-bootstrap" "../lisp/emacs-lisp/bytecomp.el"))
>     command-line()
>     normal-top-level()
>
> Am I doing something wrong?

Actually no, 7f74ed4912 fix for me.

Thanks

  Andrea

Message #11 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Mon, 15 Mar 2021 19:26:00 +0200

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: 47161 <at> debbugs.gnu.org
> Date: Mon, 15 Mar 2021 15:48:01 +0000
> 
> >   $ emacs -batch -l comp -f batch-byte-native-compile-for-bootstrap ../lisp/emacs-lisp/bytecomp.el
> >   Debugger entered--Lisp error: (wrong-type-argument "../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>)
> >     signal(wrong-type-argument ("../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>))
> >     comp--native-compile("../lisp/emacs-lisp/bytecomp.el")
> >     batch-native-compile()
> >     batch-byte-native-compile-for-bootstrap()
> >     command-line-1(("-l" "comp" "-f" "batch-byte-native-compile-for-bootstrap" "../lisp/emacs-lisp/bytecomp.el"))
> >     command-line()
> >     normal-top-level()
> >
> > Am I doing something wrong?
> 
> Actually no, 7f74ed4912 fix for me.

And I guess we also need a similar fix in byte-opt.el?  I installed
it.

I also suddenly see another byte-compilation message:

    ELC      emacs-lisp/byte-opt.elc
  Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
  Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")

What causes this?

Message #14 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Mon, 15 Mar 2021 20:05:10 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Andrea Corallo <akrl <at> sdf.org>
>> Cc: 47161 <at> debbugs.gnu.org
>> Date: Mon, 15 Mar 2021 15:48:01 +0000
>> 
>> >   $ emacs -batch -l comp -f batch-byte-native-compile-for-bootstrap ../lisp/emacs-lisp/bytecomp.el
>> >   Debugger entered--Lisp error: (wrong-type-argument "../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>)
>> >     signal(wrong-type-argument ("../lisp/emacs-lisp/bytecomp.el" listp #<subr byte-compile-form>))
>> >     comp--native-compile("../lisp/emacs-lisp/bytecomp.el")
>> >     batch-native-compile()
>> >     batch-byte-native-compile-for-bootstrap()
>> >     command-line-1(("-l" "comp" "-f" "batch-byte-native-compile-for-bootstrap" "../lisp/emacs-lisp/bytecomp.el"))
>> >     command-line()
>> >     normal-top-level()
>> >
>> > Am I doing something wrong?
>> 
>> Actually no, 7f74ed4912 fix for me.
>
> And I guess we also need a similar fix in byte-opt.el?  I installed
> it.

Right thanks

> I also suddenly see another byte-compilation message:
>
>     ELC      emacs-lisp/byte-opt.elc
>   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
>   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
>
> What causes this?

ATM I've no idea, but it doesn't look to me evidently related to native
compilation.  How can I reproduce it?

Also, shouldn't byte-opt.el be native compiled as it's in COMPILE_FIRST?

Thanks

  Andrea

Message #17 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Tue, 16 Mar 2021 14:50:53 +0200

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: 47161 <at> debbugs.gnu.org
> Date: Mon, 15 Mar 2021 20:05:10 +0000
> 
> >     ELC      emacs-lisp/byte-opt.elc
> >   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
> >   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
> >
> > What causes this?
> 
> ATM I've no idea, but it doesn't look to me evidently related to native
> compilation.  How can I reproduce it?

What I did was modified byte-opt.el, saved, and said "make".

> Also, shouldn't byte-opt.el be native compiled as it's in COMPILE_FIRST?

That bothers me as well.  It happens from time to time: for example,
I've just updated from Git, which brought modified bytecomp.el and
comp.el, both in COMPILE_FIRST.  And yet this is what I see when I say
"make":

  make -C lisp all
  make[1]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
  make -C ../leim all EMACS="../src/emacs.exe"
  make -C ../admin/grammars all EMACS="../../src/emacs.exe"
  make[2]: Entering directory `/d/gnu/git/emacs/native-comp/admin/grammars'
  make[2]: Nothing to be done for `all'.
  make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/admin/grammars'
  make[2]: Entering directory `/d/gnu/git/emacs/native-comp/leim'
  make[2]: Nothing to be done for `all'.
  make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/leim'
  make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
    ELC      emacs-lisp/bytecomp.elc
  make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
  make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
    ELC      emacs-lisp/comp.elc
  make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
  make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
  make[2]: Nothing to be done for `compile-targets'.
  make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'

Why not "ELC+ELN"?

Note that this happens when we do "make -C lisp all" from the src
directory.

Message #20 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Tue, 16 Mar 2021 16:22:01 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Andrea Corallo <akrl <at> sdf.org>
>> Cc: 47161 <at> debbugs.gnu.org
>> Date: Mon, 15 Mar 2021 20:05:10 +0000
>> 
>> >     ELC      emacs-lisp/byte-opt.elc
>> >   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
>> >   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
>> >
>> > What causes this?
>> 
>> ATM I've no idea, but it doesn't look to me evidently related to native
>> compilation.  How can I reproduce it?
>
> What I did was modified byte-opt.el, saved, and said "make".

I can reproduce it.

>> Also, shouldn't byte-opt.el be native compiled as it's in COMPILE_FIRST?
>
> That bothers me as well.  It happens from time to time: for example,
> I've just updated from Git, which brought modified bytecomp.el and
> comp.el, both in COMPILE_FIRST.  And yet this is what I see when I say
> "make":
>
>   make -C lisp all
>   make[1]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
>   make -C ../leim all EMACS="../src/emacs.exe"
>   make -C ../admin/grammars all EMACS="../../src/emacs.exe"
>   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/admin/grammars'
>   make[2]: Nothing to be done for `all'.
>   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/admin/grammars'
>   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/leim'
>   make[2]: Nothing to be done for `all'.
>   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/leim'
>   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
>     ELC      emacs-lisp/bytecomp.elc
>   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
>   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
>     ELC      emacs-lisp/comp.elc
>   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
>   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
>   make[2]: Nothing to be done for `compile-targets'.
>   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
>
> Why not "ELC+ELN"?

AFAICS using "make V=1" we fail only to add the correct "ELC+ELN" in
place of "ELC" but we invoke the right command, will try to have a look.

Regarding the macro expansion issue I tried to have a quick look but I'm
not very much into cl-generic.el and couldn't spot any obvious (for me)
issue so far.

  Andrea

Message #23 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 47161 <at> debbugs.gnu.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Tue, 16 Mar 2021 20:29:20 +0200

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: 47161 <at> debbugs.gnu.org
> Date: Tue, 16 Mar 2021 16:22:01 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > What I did was modified byte-opt.el, saved, and said "make".
> 
> I can reproduce it.

Good news, thanks.

> >> Also, shouldn't byte-opt.el be native compiled as it's in COMPILE_FIRST?
> >
> > That bothers me as well.  It happens from time to time: for example,
> > I've just updated from Git, which brought modified bytecomp.el and
> > comp.el, both in COMPILE_FIRST.  And yet this is what I see when I say
> > "make":
> >
> >   make -C lisp all
> >   make[1]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> >   make -C ../leim all EMACS="../src/emacs.exe"
> >   make -C ../admin/grammars all EMACS="../../src/emacs.exe"
> >   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/admin/grammars'
> >   make[2]: Nothing to be done for `all'.
> >   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/admin/grammars'
> >   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/leim'
> >   make[2]: Nothing to be done for `all'.
> >   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/leim'
> >   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> >     ELC      emacs-lisp/bytecomp.elc
> >   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> >   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> >     ELC      emacs-lisp/comp.elc
> >   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> >   make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> >   make[2]: Nothing to be done for `compile-targets'.
> >   make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> >
> > Why not "ELC+ELN"?
> 
> AFAICS using "make V=1" we fail only to add the correct "ELC+ELN" in
> place of "ELC" but we invoke the right command, will try to have a look.

Thanks.

> Regarding the macro expansion issue I tried to have a quick look but I'm
> not very much into cl-generic.el and couldn't spot any obvious (for me)
> issue so far.

Perhaps Stefan could help us out here.

Message #26 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org, Andrea Corallo <akrl <at> sdf.org>
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Tue, 16 Mar 2021 21:27:11 -0400

> I also suddenly see another byte-compilation message:
>
>     ELC      emacs-lisp/byte-opt.elc
>   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
>   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
>
> What causes this?

Can you try and reproduce this while `macroexp--debug-eager` is set to
a non-nil value so we hopefully get a backtrace?

The error means we're trying to do something like
`cl-defmethod` on `(setf seq-elt)` after having defined `(setf
seq-elt)` as something like a normal function, but I can't see where
we'd define it as something else.  Neither do I understand why
`cl--block-wrapper` would go through that unless it ends up loading
`seq.el` somehow.


        Stefan

Message #29 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 47161 <at> debbugs.gnu.org, akrl <at> sdf.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Fri, 19 Mar 2021 17:28:55 +0200

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: Andrea Corallo <akrl <at> sdf.org>,  47161 <at> debbugs.gnu.org
> Date: Tue, 16 Mar 2021 21:27:11 -0400
> 
> > I also suddenly see another byte-compilation message:
> >
> >     ELC      emacs-lisp/byte-opt.elc
> >   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
> >   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
> >
> > What causes this?
> 
> Can you try and reproduce this while `macroexp--debug-eager` is set to
> a non-nil value so we hopefully get a backtrace?

Sorry, it stopped happening for me, so I cannot reproduce this
anymore.

Message #32 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Fri, 19 Mar 2021 15:58:37 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
>> Cc: Andrea Corallo <akrl <at> sdf.org>,  47161 <at> debbugs.gnu.org
>> Date: Tue, 16 Mar 2021 21:27:11 -0400
>> 
>> > I also suddenly see another byte-compilation message:
>> >
>> >     ELC      emacs-lisp/byte-opt.elc
>> >   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
>> >   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
>> >
>> > What causes this?
>> 
>> Can you try and reproduce this while `macroexp--debug-eager` is set to
>> a non-nil value so we hopefully get a backtrace?
>
> Sorry, it stopped happening for me, so I cannot reproduce this
> anymore.

Same here, disappeared.  That's suspicious

  Andrea

Message #35 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Sat, 10 Apr 2021 16:44:10 +0000

Andrea Corallo <akrl <at> sdf.org> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
>>> Cc: Andrea Corallo <akrl <at> sdf.org>,  47161 <at> debbugs.gnu.org
>>> Date: Tue, 16 Mar 2021 21:27:11 -0400
>>> 
>>> > I also suddenly see another byte-compilation message:
>>> >
>>> >     ELC      emacs-lisp/byte-opt.elc
>>> >   Compiler-macro error for cl--block-wrapper: (error "(setf seq-elt) is already defined as something else than a generic function")
>>> >   Eager macro-expansion failure: (error "(setf seq-elt) is already defined as something else than a generic function")
>>> >
>>> > What causes this?
>>> 
>>> Can you try and reproduce this while `macroexp--debug-eager` is set to
>>> a non-nil value so we hopefully get a backtrace?
>>
>> Sorry, it stopped happening for me, so I cannot reproduce this
>> anymore.
>
> Same here, disappeared.  That's suspicious

Did somebody experienced this again?

Thanks

  Andrea

Message #38 received at 47161 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47161 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>,
 akrl <at> sdf.org
Subject: Re: bug#47161: 28.0.50; [feature/native-comp] Failure to
 native-compile bytecomp.el etc.
Date: Fri, 24 Jun 2022 15:18:50 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Can you try and reproduce this while `macroexp--debug-eager` is set to
>> a non-nil value so we hopefully get a backtrace?
>
> Sorry, it stopped happening for me, so I cannot reproduce this
> anymore.

It's been a year, and this still works fine, so I guess it went away for
real, and I'm therefore closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.