unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix environment and ld?
Date: Fri, 08 Feb 2019 21:48:13 +0000	[thread overview]
Message-ID: <875ztu54v6.fsf@cbaines.net> (raw)
In-Reply-To: <CAJ3okZ1uUNhcV9Bbk0rM9xNdNCCydCc7y7yUEiaOsCRPvRUFxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]


zimoun <zimon.toutoune@gmail.com> writes:

> Hi,
>
> I am working on the package Gmsh.
>
> Well, say the upstream repo is cloned and I am following the upstream readme.
> Basically, it is a CMake build system for C++ code with some Fortran.
>
> So, if I am doing:
>   mkdir build-1 && cd build-1
>   guix environment gmsh --pure
>   cmake .. && make
>   ./gmsh -info # ok :-)
>
> If I am doing:
>   mkdir build-2 && cd build-2
>   guix environment --pure --ad-hoc \
>      cmake make binutils glibc gfortran@5.5.0 gcc@5.5.0
>   cmake .. && make
>   ./gmsh -info # ok :-)
>
> Now, I would like to build a version with PETSc.
>
>   mkdir build-3 && cd build-3
>   guix environment --pure --ad-hoc \
>      cmake make binutils glibc gfortran@5.5.0 gcc@5.5.0 \
>      petsc
>   cmake .. && make
>   ./gmsh -info # fail!

One tip, try using gcc-toolchain@5.5.0 rather than binutils, glibc and
gcc@5.5.0. I'm not quite sure why, but I've had it help me with other
compilation issues.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2019-02-08 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 19:59 guix environment and ld? zimoun
2019-02-08 21:48 ` Christopher Baines [this message]
2019-02-11 11:12   ` zimoun
2019-02-12 16:43     ` Ludovic Courtès

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=875ztu54v6.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).