unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Pierre Clouzet <pierre.clouzet@inria.fr>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: Error when installing package, CMAKE_Fortran_COMPILER could be found
Date: Thu, 11 Jan 2024 17:50:54 +0100	[thread overview]
Message-ID: <878r4v24r5.fsf@gmail.com> (raw)
In-Reply-To: <1612596752.18481399.1701337451103.JavaMail.zimbra@inria.fr>

Hi Pierre,

Sorry for the late reply.

On Thu, 30 Nov 2023 at 10:44, Pierre Clouzet <pierre.clouzet@inria.fr> wrote:

> Also, this code does not use configure/make/make install of cmake/make/make install way of installing.
> Instead I need to run a script exporting variables with a . ./script.sh command
> I was wondering if you could give me a hint about how to say in a manifest how to run such script (if possible).
> You can find such script attached.

If you have not found a way in the mean time, I do not have an answer
because I am a bit confused by your question. :-)

Do you mean run the script with some manifest.scm file as with “guix
shell -m manifest.scm” or do you mean include such script with the Guix
recipe of your package variant?

If I understand correctly, you are trying to package nextsim that needs
one specific version of Gmsh, right?

The script set_env_linux.sh reads,

--8<---------------cut here---------------start------------->8---
# 1. Before compiling, install:
# - necdf, necdfcxx, boost, openmpi, gcc11:
# sudo apt install libnetcdf-c++4 libnetcdf-dev libblas-dev liblapack-dev libboost-dev \
#	libboost-chrono-dev \ libboost-date-time-dev \ libboost-filesystem-dev \
#	libboost-iostreams-dev \ libboost-log-dev \ libboost-locale-dev \
#	libboost-math-dev \ libboost-mpi-dev \ libboost-program-options-dev \
#	libboost-regex-dev \ libboost-serialization-dev \ libboost-system-dev \ libboost-timer-dev
# - also go to dependencies/gmsh-3.0.6-source
# and run the install_gmsh_for_nextsim.sh WITHOUT changing the CMAKE_PREFIX_INSTALL variable.
# 2. Compiling:
# -check that paths listed below, fit your configuration.
# - run this script to set the environement: ". ./set_env_linux.sh" (NOT ./set_env_linux.sh)
# - run make -j${nproc}
--8<---------------cut here---------------end--------------->8---

and it is not clear:

 1. if you want or not keep the dependencies from APT or replace them by
    the ones from Guix?
 2. if you want to only build Gmsh with Guix and all the rest not?
 3. how you would like to build nextsim?

What would make sense to me would to build all using Guix; it would
mean:

 a) package the patched version of Gmsh (somehow replace
    install_gmsh_for_nextsim.sh)
 b) tweak set_env_linux.sh for making it Guix-friendly (substitute the
    various hard coded PATH by Guix ones, etc.)
 c) replace the ’build’ phase of cmake build-system by calling this
    modified script by step b.

Well, maybe I misread the question. :-)

Cheers,
simon


      reply	other threads:[~2024-01-12 12:51 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 ` Error when installing package, CMAKE_Fortran_COMPILER could be found Tobias Geerinckx-Rice
2023-11-28 15:42   ` Simon Tournier
2023-11-30  9:44     ` Pierre Clouzet
2024-01-11 16:50       ` Simon Tournier [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=878r4v24r5.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    --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).