Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

async-bytecomp-package-mode causes errors to be printed all over #147

Open
mlemerre opened this issue Sep 3, 2021 · 3 comments
Open

async-bytecomp-package-mode causes errors to be printed all over #147

mlemerre opened this issue Sep 3, 2021 · 3 comments

Comments

@mlemerre
Copy link

mlemerre commented Sep 3, 2021

To reproduce:

emacs -q

(package-initialize)
(package-reinstall 'counsel) ;; or install if not installed

;; no error

(async-bytecomp-package-mode 1)
(package-reinstall 'counsel)

Error:
In toplevel form:
counsel.el:46:1:Error: Symbol's value as variable is void: seq

(async-bytecomp-package-mode 0)
(package-reinstall 'counsel)
;; No error again

The problem is not specific to counsel, a lot of packages have the same error when compiled, always on a require form.

I had a hard time debugging this problem, which came from org-ref which loaded helm which sets this async-bytecomp-package-mode to 1!
(So maybe the problem comes from helm, I am not sure).

Thanks
Matthieu

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Sep 4, 2021 via email

@mlemerre
Copy link
Author

mlemerre commented Sep 4, 2021

I have emacs-27.1 on debian, and the problem also happens with emacs -Q.

I now have a simpler test case:
(package-initialize)
(async-byte-recompile-directory "/home/matthieu/.emacs.d/elpa/counsel-0.13.4")
(async-byte-recompile-directory "/home/matthieu/.emacs.d/elpa/async-20210823.528")

In the latter, I also have an error in a require form:
In toplevel form:
smtpmail-async.el:44:1:Error: Symbol's value as variable is void: seq
This corresponds to the (require 'smtpmail) line.

All other files seem to compile just fine.

I'll try to dig more but debugging is probably going to be tricky, due to the async nature.

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Sep 4, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants