From: Chris Keschnat via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: Compiling vterm: cc: command not found
Date: Sun, 13 Nov 2022 12:04:34 +0100 [thread overview]
Message-ID: <86bkpbnltn.fsf@catsu.it> (raw)
In-Reply-To: <27B2C53F-8701-4BBF-8AD0-70247933D1D1@tobias.gr>
Tobias Geerinckx-Rice <me@tobias.gr> writes:
>> (anymore?)
>
> Guix has never provided the 'cc' alias for GCC AFAIR.
>
> Perhaps you were previously using 'clang-toolchain', which does
> symlink cc to clang? That's something that we, Guix, explicitly add;
> not upstream.
>
> It's unfortunate that Guix promotes a non-GPL compiler over GCC this way.
>
> Kind regards,
>
> T G-R
>
> Sent on the go. Excuse or enjoy my brevity.
Hello,
I might have been confused about how I installed vterm before. I
thought I used straight.el, which builds the module as describe in my
previous mail. It could be that I had manually installed =emacs-vterm= and
didn't add it to my (guix) emacs profile.
I have now installed ~emacs-vterm~ through guix (together with ~libvterm~
in my emacs profile). When I try running vterm from emacs, it still asks
to compile the module though (which fails).
Looking at the ~emacs-vterm~ packages, this happens here:
#+begin_src sh
(unless (require 'vterm-module nil t)
....)
#+end_src
Trying manually:
#+begin_src sh
(require 'vterm-module)
=>
Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "vterm-module")
require(vterm-module)
elisp--eval-last-sexp(nil)
eval-last-sexp(nil)
funcall-interactively(eval-last-sexp nil)
command-execute(eval-last-sexp)
#+end_src
There is a .so file in my emacs profile though, so I think there is something wrong with some kind of module path?
#+begin_src sh
~/.guix-extra-profiles/emacs/emacs $ find | grep vterm-module
./lib/vterm-module.so
#+end_src
I do not know how/what to check though. So far I have only found that my
~module-file-prefix~ is ".so". But other than that, I do not know how
the loading of modules works and would appreciate a hint.
Thank you
Chris
next prev parent reply other threads:[~2022-11-13 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:14 Compiling vterm: cc: command not found Chris Keschnat via
2022-11-12 18:11 ` Csepp
2022-11-13 10:50 ` Tobias Geerinckx-Rice
2022-11-13 11:04 ` Chris Keschnat via [this message]
2022-11-22 6:56 ` Chris Keschnat via
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=86bkpbnltn.fsf@catsu.it \
--to=help-guix@gnu.org \
--cc=chris@catsu.it \
/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.
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).