unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 48021@debbugs.gnu.org
Subject: bug#48021: comp.el cannot be loaded without native compilation
Date: Mon, 26 Apr 2021 15:18:34 -0400	[thread overview]
Message-ID: <xc8s54yhv9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <xjfo8e15c4h.fsf@sdf.org> (Andrea Corallo's message of "Mon, 26 Apr 2021 14:55:26 +0000")

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.

The issue about comp.el being unloadable in builds without native
compilation remains (and hence test-custom-deps still fails).

I believe that in general, .el files should always be loadable, they
should just do nothing if not applicable.

For example, C-h f completion can try to load comp.el.





  reply	other threads:[~2021-04-26 19:18 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 [this message]
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
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=xc8s54yhv9.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=48021@debbugs.gnu.org \
    --cc=akrl@sdf.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).