From: Greg Minshall <minshall@acm.org>
To: emacs-devel@gnu.org
Subject: make check fails? (emacs-26.1 w/modules)
Date: Mon, 03 Sep 2018 17:39:14 +0300 [thread overview]
Message-ID: <16923.1535985554@minshall-apollo.minshall.org> (raw)
hi. from git://git.sv.gnu.org/emacs.git i've checked out emacs-26.1. i
configure with modules, to wit:
: ./configure --with-xwidgets --with-modules --without-dbus
"make" works, but "make check" fails:
----
CCLD data/emacs-module/mod-test.so
ELC src/emacs-module-tests.elc
In toplevel form:
src/emacs-module-tests.el:32:1:Error: Loading file /home/minshall/src/import/emacs/git/emacs/lisp/emacs-lisp/ert.elc failed to provide feature `mod-test'
Makefile:148: recipe for target 'src/emacs-module-tests.elc' failed
make[3]: *** [src/emacs-module-tests.elc] Error 1
make[3]: Target 'src/emacs-module-tests.log' not remade because of errors.
----
(i think, btw, the pointer at ".../ert.elc" is misguided; see
parenthetical a bit below.)
if i do the following:
----
mod-test-file
"/home/minshall/src/import/emacs/git/emacs/test/data/emacs-module/mod-test"
(require 'mod-test mod-test-file)
----
i get an error
----
Debugger entered--Lisp error: (error "Loading file
/usr/local/share/emacs/26.1/lisp/vc/log-edit.elc failed to provide
feature ‘mod-test’")
----
(as noted above, note the seemingly random reference to log-edit.elc.)
the only thing i notice odd is that test/data/emacs-module/mod-test.c,
when (presumably) registering, calls : provide (env, "mod-test"); rather
than some variant of Fprovide(). but, since i don't really know how
modules are expected to behave, i can't really say.
any clues would be gratefully imbibed.
cheers, Greg
ps -- if there's some politer, prettier way to interleave code/results
with e-mail text, i'd be interested to hear. i find my style a bit hard
to parse.
next reply other threads:[~2018-09-03 14:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 14:39 Greg Minshall [this message]
2018-09-03 15:12 ` make check fails? (emacs-26.1 w/modules) Greg Minshall
2018-09-03 15:13 ` Eli Zaretskii
2018-09-03 15:16 ` Greg Minshall
2018-09-03 15:18 ` Greg Minshall
2018-09-04 10:39 ` Greg Minshall
2018-09-05 7:54 ` Paul Eggert
2018-09-05 9:14 ` Greg Minshall
2018-09-05 20:26 ` Greg Minshall
2018-09-05 20:55 ` Paul Eggert
2018-09-06 8:58 ` Robert Pluim
2018-09-06 10:32 ` Greg Minshall
2018-09-12 13:41 ` Robert Pluim
2018-09-12 14:56 ` Paul Eggert
2018-09-12 16:19 ` Greg Minshall
2018-09-12 16:37 ` Robert Pluim
2018-09-12 16:27 ` Greg Minshall
2018-09-12 16:39 ` Robert Pluim
2018-09-07 9:10 ` Greg Minshall
2018-09-03 18:27 ` Paul Eggert
2018-09-03 23:46 ` Greg Minshall
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=16923.1535985554@minshall-apollo.minshall.org \
--to=minshall@acm.org \
--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 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).