* native-comp bytecode error
@ 2020-05-26 10:02 Alex Bennée
2020-05-26 11:17 ` Noam Postavsky
0 siblings, 1 reply; 3+ messages in thread
From: Alex Bennée @ 2020-05-26 10:02 UTC (permalink / raw)
To: Andrea Corallo, Paul Eggert; +Cc: emacs-devel
Hi,
When I updated my native-comp branch I ran into an error:
read(#<buffer *load*-542126>)
eval-buffer(#<buffer *load*-542126> nil "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t) ; Reading at buffer position 38978
load-with-code-conversion("/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t)
require(use-package-core)
eval-buffer(#<buffer *load*-856510> nil "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t) ; Reading at buffer position 1695
load-with-code-conversion("/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t)
require(use-package)
eval-buffer(#<buffer *load*-418973> nil "/home/alex/.emacs.d/my-elisp/my-package.el" nil t) ; Reading at buffer position 1988
load-with-code-conversion("/home/alex/.emacs.d/my-elisp/my-package.el" "/home/alex/.emacs.d/my-elisp/my-package.el" nil nil)
load-library("my-package.el")
eval-buffer(#<buffer *load*> nil "/home/alex/.emacs.d/init.el" nil t) ; Reading at buffer position 1262
load-with-code-conversion("/home/alex/.emacs.d/init.el" "/home/alex/.emacs.d/init.el" t t)
load("/home/alex/.emacs.d/init" noerror nomessage)
startup--load-user-init-file(#f(compiled-function () #<bytecode 0xee7067c466618d7>) #f(compiled-function () #<bytecode 0x81a392fa1b0fd93>) t)
command-line()
normal-top-level()
After trying a clean re-build and a re-init of ELPA I ended up bisecting
it to:
bad f0b0105d913a94c66f230874c9269b19dbbc83bd
Author: Paul Eggert <eggert@cs.ucla.edu>
AuthorDate: Tue May 19 23:22:40 2020 -0700
Commit: Paul Eggert <eggert@cs.ucla.edu>
CommitDate: Tue May 19 23:25:16 2020 -0700
Parent: 5352bda4eeb Add test for bug#39680
Merged: (no branch, bisect started on feature/native-comp) emacs-26 emacs-27
master test-base
Contained: feature/native-comp
Follows: emacs-27.0.91 (955)
Hoist some byte-code checking out of eval
Looking at the diff I guess there is a byte-code ABI change although I
had completely reset my elpa directory and removed any .elc files I
could find in my own path.
Falling back to the previous commit I can start emacs again although I
did notice this in my messages:
Error running timer: (wrong-type-argument plistp ((package-install . ivy-rich--package-install-transformer) (counsel-recentf . ivy-rich--counsel-recentf-transformer) (counsel-find-file . ivy-rich--counsel-find-file-transformer) (ivy-switch-buffer . ivy-rich--ivy-switch-buffer-transformer) (counsel-fonts . counsel--font-with-sample) (counsel-rg . counsel-git-grep-transformer) (counsel-pt . counsel-git-grep-transformer) (counsel-ag . counsel-git-grep-transformer) (counsel-tracker . counsel-tracker-transformer) (counsel-buffer-or-recentf . counsel-buffer-or-recentf-transformer) (counsel-git-grep . counsel-git-grep-transformer) (counsel-M-x . ivy-rich--counsel-M-x-transformer) (counsel-describe-function . ivy-rich--counsel-describe-function-transformer) (counsel-describe-variable . ivy-rich--counsel-describe-variable-transformer) (counsel-company . counsel--company-display-transformer) (internal-complete-buffer . ivy-switch-buffer-transformer) (read-file-name-internal . ivy-read-file-transformer)))
but I'm not sure if that is related or a consequence of rebuilding all
of elpa.
--
Alex Bennée
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: native-comp bytecode error
2020-05-26 10:02 native-comp bytecode error Alex Bennée
@ 2020-05-26 11:17 ` Noam Postavsky
2020-05-26 11:44 ` Alex Bennée
0 siblings, 1 reply; 3+ messages in thread
From: Noam Postavsky @ 2020-05-26 11:17 UTC (permalink / raw)
To: Alex Bennée; +Cc: Paul Eggert, Emacs developers, Andrea Corallo
On Tue, 26 May 2020 at 06:02, Alex Bennée <alex.bennee@linaro.org> wrote:
> When I updated my native-comp branch I ran into an error:
>
> read(#<buffer *load*-542126>)
> eval-buffer(#<buffer *load*-542126> nil "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t) ; Reading at buffer position 38978
You haven't show the actual error, but perhaps this is the use-package
bug (accidentally uses a byte code literal #[...] where a vector
literal [...] was meant)?
https://lists.gnu.org/archive/html/emacs-devel/2020-05/msg02859.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: native-comp bytecode error
2020-05-26 11:17 ` Noam Postavsky
@ 2020-05-26 11:44 ` Alex Bennée
0 siblings, 0 replies; 3+ messages in thread
From: Alex Bennée @ 2020-05-26 11:44 UTC (permalink / raw)
To: Noam Postavsky; +Cc: Paul Eggert, Emacs developers, Andrea Corallo
Noam Postavsky <npostavs@gmail.com> writes:
> On Tue, 26 May 2020 at 06:02, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>> When I updated my native-comp branch I ran into an error:
>>
>> read(#<buffer *load*-542126>)
>> eval-buffer(#<buffer *load*-542126> nil "/home/alex/.emacs.d/elpa/use-package-2.4/use-packa..." nil t) ; Reading at buffer position 38978
>
> You haven't show the actual error, but perhaps this is the use-package
> bug (accidentally uses a byte code literal #[...] where a vector
> literal [...] was meant)?
Ahh it could be - I have use-package pinned to stable so I don't think
that fix has come through there yet. I guess I should just track melpa
like the rest of the packages I have here...
>
> https://lists.gnu.org/archive/html/emacs-devel/2020-05/msg02859.html
--
Alex Bennée
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-05-26 11:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-26 10:02 native-comp bytecode error Alex Bennée
2020-05-26 11:17 ` Noam Postavsky
2020-05-26 11:44 ` Alex Bennée
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).