From: Greg Minshall <minshall@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: make check fails? (emacs-26.1 w/modules)
Date: Mon, 03 Sep 2018 18:12:40 +0300 [thread overview]
Message-ID: <21034.1535987560@minshall-apollo.minshall.org> (raw)
In-Reply-To: Your message of "Mon, 03 Sep 2018 17:39:14 +0300." <16923.1535985554@minshall-apollo.minshall.org>
oops. i take back my one observation:
> 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.
as it turns out, provide() is provided in mod-test.c itself, as a
wrapper for, essentially, Qprovide(), which i guess to be correct.
btw, i should have mentioned that the dynamic library for mod-test
appears to exist, have emacs_module_init in it:
----
bash minshall-apollo: {1184} ls -l test/data/emacs-module/mod-test.so
-rwxrwxr-x 1 minshall minshall 68712 Sep 3 17:23 test/data/emacs-module/mod-test.so*
bash minshall-apollo: {1185} nm test/data/emacs-module/mod-test.so | grep emacs_module_init
0000000000000ee0 T emacs_module_init
----
cheers, Greg
next prev parent reply other threads:[~2018-09-03 15:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 14:39 make check fails? (emacs-26.1 w/modules) Greg Minshall
2018-09-03 15:12 ` Greg Minshall [this message]
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=21034.1535987560@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).