From: Chris Keschnat via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Compiling vterm: cc: command not found
Date: Sat, 12 Nov 2022 16:14:37 +0100 [thread overview]
Message-ID: <865yfkfb89.fsf@catsu.it> (raw)
Hello, after todays ~guix pull~, I cannot compile vterm anymore. I do not
seem to have ~cc~ installed (anymore?). Am I missing a package? I have
~make~, ~cmake~, ~gcc~, and ~gcc-toolchain~ installed and didn't change
anything on that front.
Steps to reproduce (following the "Manual installation" from the docs[1]):
#+begin_src sh
git clone https://github.com/akermu/emacs-libvterm.git
cd emacs-libvterm
mkdir -p build
cd build
cmake ..
make
#+end_src
Results in:
#+begin_src sh
[ 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
/home/ck/.guix-profile/bin/libtool: line 1933: cc: command not found
make[3]: *** [Makefile:63: src/encoding.lo] Error 1
make[2]: *** [CMakeFiles/libvterm.dir/build.make:86: libvterm-prefix/src/libvterm-stamp/libvterm-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:112: CMakeFiles/libvterm.dir/all] Error 2
make: *** [Makefile:91: all] Error 2
#+end_src
[1] https://github.com/akermu/emacs-libvterm
Thanks
Chris
next reply other threads:[~2022-11-12 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:14 Chris Keschnat via [this message]
2022-11-12 18:11 ` Compiling vterm: cc: command not found 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
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=865yfkfb89.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).