unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: mike@rohleder.de
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: 35644@debbugs.gnu.org
Subject: bug#35644: emacs module support doesn't work
Date: Tue, 10 Mar 2020 17:52:12 +0100	[thread overview]
Message-ID: <878sk8qhj7.fsf@rohleder.de> (raw)
In-Reply-To: <87o94cid7z.fsf@cune.org> (Caleb Ristvedt's message of "Wed, 08 May 2019 21:16:48 -0500")

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Caleb Ristvedt <caleb.ristvedt@cune.org> writes:
>
> Assuming the above file is named emacs-module-test.c:
>
> -------------------------------
> $ gcc -fPIC -shared emacs-module-test.c -o hello-module.so
> $ emacs -Q -L . --batch -l hello-module --eval "(message (hello-c))"
>
> => Symbol's function definition is void: hello-c
> -------------------------------
>
> As far as I can tell, this should work. Our emacs is built with
> '--with-modules', and 'MODULES' is in system-configuration-features. Any
> idea what's going wrong?

I cant reproduce this, it works for me:

$ guix environment -C bash --ad-hoc emacs gcc-toolchain
[env]$ gcc -fPIC -shared emacs-module-test.c -o hello-module.so
[env]$ emacs -Q -L . --batch -l hello-module --eval "(message (hello-c))"  
TEST MESSAGE!
TEST MESSAGE!
TEST MESSAGE!
Hello Emacs


-- 
Der Erfolg ist nicht danach zu beurteilen, was ein Mensch im Leben
erreicht hat, sondern nach den Hindernissen, die er auf dem Weg zum
Erfolg ueberwunden hat.
(Booker T. Washington)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-03-10 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  2:16 bug#35644: emacs module support doesn't work Caleb Ristvedt
2020-03-10 16:52 ` mike [this message]
2020-03-11  5:55   ` Caleb Ristvedt
2020-03-20 19:06     ` Marius Bakke

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878sk8qhj7.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=35644@debbugs.gnu.org \
    --cc=caleb.ristvedt@cune.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/guix.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).