bug#35644: emacs module support doesn't work

2020-03-20 Thread Marius Bakke
Caleb Ristvedt writes: > I can confirm that it now works. I did a bit of looking through the commit > history and playing around with 'guix time-machine', and whatever changed > to fix > it, it wasn't a change that touched gnu/packages/emacs.scm. I know it fell > between 7ab5c4e0e8 and 5ce153b110

bug#35644: emacs module support doesn't work

2020-03-10 Thread Caleb Ristvedt
I can confirm that it now works. I did a bit of looking through the commit history and playing around with 'guix time-machine', and whatever changed to fix it, it wasn't a change that touched gnu/packages/emacs.scm. I know it fell between 7ab5c4e0e8 and 5ce153b110, though. Thanks for bringing this

bug#35644: emacs module support doesn't work

2020-03-10 Thread mike
Caleb Ristvedt 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: hell

bug#35644: emacs module support doesn't work

2019-05-08 Thread Caleb Ristvedt
While attempting to package libegit2 (https://github.com/magit/libegit2), I found that any attempt at loading a dynamic module from emacs would seemingly work (it returns t), but not actually work: no module api functions invoked from C seem to have any effect, including defining functions and prin