From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Pierre Clouzet <pierre.clouzet@inria.fr>, help-guix@gnu.org
Cc: control@debbugs.gnu.org
Subject: Error when installing package, CMAKE_Fortran_COMPILER could be found
Date: Fri, 24 Nov 2023 16:53:42 +0000 [thread overview]
Message-ID: <C69E484D-E100-4592-A4BF-D55DC0D0B49A@tobias.gr> (raw)
In-Reply-To: <441964777.14793216.1700756479745.JavaMail.zimbra@inria.fr>
close 67416
thanks
(The above is for the Debbugs control bot. The bug-guix@ address is for reporting shortcomings in Guix. For general support, please use help-guix@. I've moved this discussion there.)
Hi Pierre,
It appears that you haven't given the package a FORTRAN compiler to find. Try
(native-inputs (list gfortran))
to add one to the build environment. Do not waste time 'guix install'ing anything, this will have 0 effect.
If the build system still won't find gfortran, try
(arguments
`(
...
#:phases
(modify-phases %standard-phases
(add-before 'configure 'find-gfortran
(lambda _
(setenv "FC" (which "gfortran"))))))
or so. Untested example, assuming the compiler binary is also named 'gfortran'.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next parent reply other threads:[~2023-11-24 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <441964777.14793216.1700756479745.JavaMail.zimbra@inria.fr>
2023-11-24 16:53 ` Tobias Geerinckx-Rice [this message]
2023-11-28 15:42 ` Error when installing package, CMAKE_Fortran_COMPILER could be found Simon Tournier
2023-11-30 9:44 ` Pierre Clouzet
2024-01-11 16:50 ` Simon Tournier
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=C69E484D-E100-4592-A4BF-D55DC0D0B49A@tobias.gr \
--to=me@tobias.gr \
--cc=control@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=pierre.clouzet@inria.fr \
/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).