jwiegley / emacs-async

Simple library for asynchronous processing in Emacs
GNU General Public License v3.0
837 stars 68 forks source link

Cannot byte-compile emacs-async on Emacs 25 and 27 #136

Closed c4eater closed 3 years ago

c4eater commented 3 years ago

Hi, Apparently, emacs-async cannot be byte-compiled under Emacs other than v26. I'm using the git upstream.

Under Emacs 27, "make" breaks on the autoloads target: Wrong type argument: stringp, nil

Under Emacs 26, "make" works fine.

Under Emacs 25, "make" generates the autoloads, but subsequent byte-compilation emits a bunch of errors: Error: Cannot open load file: cl-lib

Thanks

c4eater commented 3 years ago

Apologies, I didn't sync up with git master. This was fixed by 14f48de.

thierryvolpiatto commented 3 years ago

c4eater notifications@github.com writes:

Hi, Apparently, emacs-async cannot be byte-compiled under Emacs other than v26. I'm using the git upstream.

Under Emacs 27, "make" breaks on the autoloads target: Wrong type argument: stringp, nil

Can't reproduce, make works fine on emacs-27.

Under Emacs 26, "make" works fine.

Under Emacs 25, "make" generates the autoloads, but subsequent byte-compilation emits a bunch of errors: Error: Cannot open load file: cl-lib

I have no more emacs-25 to try so I can't tell, but well emacs-25 is now far behind us...

-- Thierry

thierryvolpiatto commented 3 years ago

c4eater notifications@github.com writes:

Hi, Apparently, emacs-async cannot be byte-compiled under Emacs other than v26. I'm using the git upstream.

Which git upstream?

An issue on Makefile for emacs-27 have been fixed on github by 14f48de commit, is it the one you are using?

Under Emacs 27, "make" breaks on the autoloads target: Wrong type argument: stringp, nil

Under Emacs 26, "make" works fine.

Under Emacs 25, "make" generates the autoloads, but subsequent byte-compilation emits a bunch of errors: Error: Cannot open load file: cl-lib

Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.*

-- Thierry