2
0
Fork
You've already forked chez
0

Cannot load generated autoload file by `make-directory-autoloads' #7

Open
opened 2021年08月04日 10:12:57 +02:00 by yoctocell · 3 comments
yoctocell commented 2021年08月04日 10:12:57 +02:00 (Migrated from gitlab.com)
Copy link

When trying to package geiser-chez in Guix, Emacs fails to load the generated autoload file.

;;; geiser-chez-autoloads.el --- automatically extracted autoloads
;;
;;; Code:

;;;### (autoloads nil "geiser-chez" "geiser-chez.el" (0 1 0 0))
;;; Generated autoloads from geiser-chez.el
(geiser-implementation-extension 'chez "def")
(geiser-activate-implementation 'chez)
(autoload 'run-chez "geiser-chez" "\
Start a Geiser Chez REPL." t)
(autoload 'switch-to-chez "geiser-chez" "\
Start a Geiser Chez REPL, or switch to a running one." t)
(if (fboundp 'register-definition-prefixes) (register-definition-prefixes "geiser-chez" '("chez" "geiser-chez-")))
;;;***

(provide 'geiser-chez-autoloads)
;; Local Variables:
;; version-control: never
;; no-update-autoloads: t
;; coding: utf-8
;; End:
;;; geiser-chez-autoloads.el ends here
[...]
Compiling /gnu/store/qvqa5g5a54zbj6qhppfqzf62jlhn6gn7-emacs-geiser-chez-0.16/share/emacs/site-lisp/geiser-chez-0.16/geiser-chez-autoloads.el...
In end of data:
geiser-chez-autoloads.el:30:1:Warning: the following functions are not known
 to be defined: geiser-implementation-extension,
 geiser-activate-implementation

We have to solve this by patching1 the generated autoload file; is there something that upstream could do to solve this issue. I think geiser-racket has the same problem2.

Thanks

When trying to package geiser-chez in Guix, Emacs fails to load the generated autoload file. ``` ;;; geiser-chez-autoloads.el --- automatically extracted autoloads ;; ;;; Code: ;;;### (autoloads nil "geiser-chez" "geiser-chez.el" (0 1 0 0)) ;;; Generated autoloads from geiser-chez.el (geiser-implementation-extension 'chez "def") (geiser-activate-implementation 'chez) (autoload 'run-chez "geiser-chez" "\ Start a Geiser Chez REPL." t) (autoload 'switch-to-chez "geiser-chez" "\ Start a Geiser Chez REPL, or switch to a running one." t) (if (fboundp 'register-definition-prefixes) (register-definition-prefixes "geiser-chez" '("chez" "geiser-chez-"))) ;;;*** (provide 'geiser-chez-autoloads) ;; Local Variables: ;; version-control: never ;; no-update-autoloads: t ;; coding: utf-8 ;; End: ;;; geiser-chez-autoloads.el ends here ``` ``` [...] Compiling /gnu/store/qvqa5g5a54zbj6qhppfqzf62jlhn6gn7-emacs-geiser-chez-0.16/share/emacs/site-lisp/geiser-chez-0.16/geiser-chez-autoloads.el... In end of data: geiser-chez-autoloads.el:30:1:Warning: the following functions are not known to be defined: geiser-implementation-extension, geiser-activate-implementation ``` We have to solve this by patching[1] the generated autoload file; is there something that upstream could do to solve this issue. I think geiser-racket has the same problem[2]. Thanks [1]: https://issues.guix.gnu.org/49819 [2]: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/emacs-xyz.scm?id=6e99e113e6f0852b627f9cfb71e5fc3d14573639#n386
jaor commented 2021年08月04日 15:33:31 +02:00 (Migrated from gitlab.com)
Copy link

We have to solve this by patching[1] the generated autoload file; is
there something that upstream could do to solve this issue.

i hope so, yes. thanks for the report, i'll get to it soon as i can.

> We have to solve this by patching[1] the generated autoload file; is > there something that upstream could do to solve this issue. i hope so, yes. thanks for the report, i'll get to it soon as i can.
jaor commented 2021年08月04日 20:37:22 +02:00 (Migrated from gitlab.com)
Copy link

i took a look and i don't see what's to be fixed. the functions that
are not defined are autoloaded in geiser.el, so the corresponding
autoloads for geiser core should take care of that. since geiser-chez
depends on geiser, i would expect the latter's autoloads are in place
when the former kick? (i'm afraid i know nothing about guix packaging,
so i might be missing something here).

i took a look and i don't see what's to be fixed. the functions that are not defined are autoloaded in geiser.el, so the corresponding autoloads for geiser core should take care of that. since geiser-chez depends on geiser, i would expect the latter's autoloads are in place when the former kick? (i'm afraid i know nothing about guix packaging, so i might be missing something here).
yoctocell commented 2021年08月07日 17:27:12 +02:00 (Migrated from gitlab.com)
Copy link

jao commented:

i took a look and i don't see what's to be fixed. the functions that
are not defined are autoloaded in geiser.el, so the corresponding
autoloads for geiser core should take care of that. since geiser-chez
depends on geiser, i would expect the latter's autoloads are in place
when the former kick? (i'm afraid i know nothing about guix packaging,
so i might be missing something here).

Its a bit weird that this problem occurs with geiser-chez and
geiser-racket, but not with geiser-guile. I am not that familiar with
autoloads in Elisp, but I will look into it.

Thanks for looking into this!

> jao commented: > > > i took a look and i don't see what's to be fixed. the functions that > are not defined are autoloaded in geiser.el, so the corresponding > autoloads for geiser core should take care of that. since geiser-chez > depends on geiser, i would expect the latter's autoloads are in place > when the former kick? (i'm afraid i know nothing about guix packaging, > so i might be missing something here). Its a bit weird that this problem occurs with geiser-chez and geiser-racket, but not with geiser-guile. I am not that familiar with autoloads in Elisp, but I will look into it. Thanks for looking into this!
Sign in to join this conversation.
No Branch/Tag specified
master
0.18
0.17
0.16
0.14
0.13
0.12
0.11.2
0.11.1
0.11
0.10
0.9
0.8.1
0.8
0.7
0.6
0.5
0.4
0.3
0.2.2
0.2.1
0.2
0.1.4
0.1.3
0.1.2
0.1.1
0.1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geiser/chez#7
Reference in a new issue
geiser/chez
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?