Re: Compiling vterm: cc: command not found

[Csepp <raingloom@riseup.net>]

Chris Keschnat via <help-guix@gnu.org> writes:

> 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

Without having looked at the package, what I would recommend and what I
usually try in a case when something tries to use cc is set the CC
environment variable or configure flag.  Its value should ideally be
#$(cc-for-target).
So you would have something like in modify-phases:
(add-before 'configure 'set-cc
(lambda _ (setenv "CC" #$(cc-for-target))))