-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot open load file: No such file or directory, vterm-module #113
Comments
FYI, I changed my configure line to include Here's my final configure line:
Leaving this open in case a check or readme addition should be added? thanks |
Ditto -- just cloned and installed (on Ubuntu 19.04, emacs 26.1) and all I got to show now is 'No such file or directory, vterm-module'. Any hints? |
@eddelbuettel Could you verify that |
@akermu Asking |
@eddelbuettel It does require a custom build as neither the ubuntu nor the debian package have modules support enabled. You might want to try to compile emacs with modules support, it's very easy: git clone git://git.sv.gnu.org/emacs.git
cd emacs
git checkout emacs-26.2
./autogen.sh
./configure --with-modules
make |
Thanks for the clarification. I'll wait til the maintainer of the Emacs package decides to adopt modules. |
OS: MacOS
Emacs Version 27.0.50 (9.0) compiled from source with the following configure options:
As in the subject line, i'm getting Cannot open load file: No such file or directory, vterm-module.
Followed the master branches README instructions exactly, and even with a
make run
still getting said error.Is there some shared library setting I need to be compiling with? I'm not exactly sure how shared/linked libraries work on osx/with emacs/etc.
I have read and tried some suggestions from #92, and #85 to no avail (yet). I'll play with it a bit more this evening.
Any tips appreciated, -Joe
Update
I just downloaded 26.2 from emacsformacos.com and vterm started without any issues.... It's either something regarding 27.x or my compile options. Still investigating.
The text was updated successfully, but these errors were encountered: