From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 48021@debbugs.gnu.org
Subject: bug#48021: comp.el cannot be loaded without native compilation
Date: Mon, 26 Apr 2021 21:16:09 +0000 [thread overview]
Message-ID: <xjf4kfs4uhy.fsf@sdf.org> (raw)
In-Reply-To: <xjfeeew4wng.fsf@sdf.org> (Andrea Corallo via's message of "Mon, 26 Apr 2021 20:29:39 +0000")
Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> Andrea Corallo wrote:
>>
>>>> ./src/emacs -Q -l ./lisp/emacs-lisp/comp.el
>>>>
>>>> memq: Symbol's value as variable is void: comp-ctxt
>>
>>> with a390a4965f comp-cstr-tests run clean for me also on vanilla build,
>>> please let me know if this is sufficient for the case you are testing.
>>
>> Thanks. comp-cstr-test-70 is still failing for me.
>
> Could you share the invocation you are using? I'm asking cause here on
> 449045b2a6 I see this passing.
>
>>
>> The issue about comp.el being unloadable in builds without native
>> compilation remains (and hence test-custom-deps still fails).
>
> I didn't know about the test-custom-deps, I'll have a look.
Hi Glenn,
with 40c71e574a comp-cstr.el and comp.el are loadable for me also on
vanilla builds, please have a look.
Thanks
Andrea
next prev parent reply other threads:[~2021-04-26 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 0:43 bug#48021: comp.el cannot be loaded without native compilation Glenn Morris
2021-04-26 14:55 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-26 19:18 ` Glenn Morris
2021-04-26 20:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-26 21:16 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-04-27 4:56 ` Glenn Morris
2021-04-29 18:44 ` Glenn Morris
2021-04-29 19:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 23:40 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjf4kfs4uhy.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48021@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=rgm@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 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).