From: Adam Porter <adam@alphapapa.net>
To: emacs-devel <emacs-devel@gnu.org>
Subject: [native-comp] Small, new bug with macros?
Date: Sun, 5 Apr 2020 09:01:53 -0500 [thread overview]
Message-ID: <CAO_b3FVhf7UO+r1G5aac=oG=2cWtFpmK+hMYH-K1mfEjpBzbgQ@mail.gmail.com> (raw)
Hi Andrea,
I've been testing the latest Docker image with the deferred
compilation. I noticed what may be a small, new bug. To reproduce,
you could use this code:
(setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")
("melpa" . "https://melpa.org/packages/")))
(package-initialize)
(package-install 'quelpa-use-package)
(use-package bufler
:quelpa
(bufler :fetcher github :repo "alphapapa/bufler.el"
:files (:defaults (:exclude "helm-bufler.el"))))
In the *Async-native-compile-log* buffer, I see:
Compiling /home/me/tmp/src/emacs/native-comp/.emacs.d/elpa/bufler-20200405.1230/bufler.el...
Symbol's function definition is void: bufler-defauto-group
bufler-defauto-group is a macro, not a function, and it is defined
before it is called, so I don't understand why the error is happening.
The package loads and works fine in its byte-compiled form, and the
error didn't happen when I was using an earlier Docker image from a
few weeks ago.
Thanks,
Adam
next reply other threads:[~2020-04-05 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 14:01 Adam Porter [this message]
2020-04-05 14:12 ` [native-comp] Small, new bug with macros? Andrea Corallo
2020-04-05 14:41 ` Adam Porter
2020-04-06 20:45 ` Andrea Corallo
2020-04-07 14:30 ` Expansion of macros at compile time in eval-and-compile bodies (was: Re: [native-comp] Small, new bug with macros?) Adam Porter
2020-04-07 15:26 ` Expansion of macros at compile time in eval-and-compile bodies Stefan Monnier
2020-04-05 14:12 ` bug#40126: [native-comp] Small, new bug with macros? Andrea Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO_b3FVhf7UO+r1G5aac=oG=2cWtFpmK+hMYH-K1mfEjpBzbgQ@mail.gmail.com' \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.