Skip to content
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

Compilation fails on Mac OS when libtool is not named "glibtool" #716

Open
rome-user opened this issue Apr 20, 2024 · 1 comment
Open

Compilation fails on Mac OS when libtool is not named "glibtool" #716

rome-user opened this issue Apr 20, 2024 · 1 comment

Comments

@rome-user
Copy link

Hello,

I am currently using Nix as my package manager on a new Mac. The libtool package provides libtool binary rather than glibtool. This causes the libvterm module to fail compilation. See logs below

-- System libvterm not found: libvterm will be downloaded and compiled as part of the build process
-- Configuring done (0.3s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/*/.emacs.d/straight/build/vterm/build
[  8%] Performing update step for 'libvterm'
[ 16%] No patch step for 'libvterm'
[ 25%] No configure step for 'libvterm'
[ 33%] Performing build step for 'libvterm'
CC src/encoding.c
make[3]: glibtool: No such file or directory
make[3]: *** [src/encoding.lo] Error 1
make[2]: *** [libvterm-prefix/src/libvterm-stamp/libvterm-build] Error 2
make[1]: *** [CMakeFiles/libvterm.dir/all] Error 2
make: *** [all] Error 2

However, libtool exists and is accessible from shell

% which libtool
/Users/*/.nix-profile/bin/libtool

I have considered alternatives, such as using Nix to manage Emacs packages, but the emacs-overlay does not support Unicode characters in init.el. So installing the vterm package from Nix is not an option for me

@rome-user
Copy link
Author

On further investigation, I found that the problem lies outside of this package's control. The issue is here: https://github.com/Sbozzolo/libvterm-mirror/blob/libvterm/Makefile#L1-L5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant