From: Chris Keschnat via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: Compiling vterm: cc: command not found
Date: Tue, 22 Nov 2022 07:56:17 +0100 [thread overview]
Message-ID: <86y1s34gt6.fsf@catsu.it> (raw)
In-Reply-To: <86bkpbnltn.fsf@catsu.it>
Chris Keschnat <chris@catsu.it> writes:
> 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
As I couldn't figure out how to debug this, I chose trial and error. And
it workd. I'm not exactly sure what the issue was, but here is what I
did, in case it helps anyone in the future:
Added ~libtool~ and ~cmake~ to =emacs.scm= and installed those. After that
and running:
#+begin_src sh
GUIX_PROFILE="/home/ck/.guix-extra-profiles/emacs/emacs"
. "$GUIX_PROFILE/etc/profile"
#+end_src
the compilation worked. But the module could not be loaded:
#+begin_src sh
byte-code: Module could not be opened: "/home/ck/.emacs.d/straight/build/vterm/vterm-module.so", "libvterm.so.0: cannot open shared object file: No such file or directory"
#+end_src
Then changed (as stated in the docs)
#+begin_src emacs-lisp
(use-package vterm)
#+end_src
to
#+begin_src emacs-lisp
(use-package vterm
:load-path "/home/ck/.guix-extra-profiles/emacs/emacs/lib")
#+end_src
vterm now works again.
prev parent reply other threads:[~2022-11-22 6:58 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
2022-11-22 6:56 ` Chris Keschnat via [this message]
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=86y1s34gt6.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).