unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 04/05: gnu: petsc: Update to 3.16.1.
Date: Wed, 01 Dec 2021 23:33:10 +0100	[thread overview]
Message-ID: <875ys8ymzd.fsf@gnu.org> (raw)
In-Reply-To: <87o8604gm7.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 01 Dec 2021 14:08:48 +0100")

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

> Hey,
>
>>     * gnu/packages/maths.scm (petsc): Update to 3.16.1.
>>     [native-inputs]: Use PYTHON instead of PYTHON-2.  Add WHICH.
>>     [arguments]: Rewrite using gexps.  Pass '--with-openblas-dir'.  In
>>     'configure' phase, modify "config/example_template.py".
>
> I noticed that petsc-* packages are now part of every evaluation of
> c-u-f in Cuirass. Any chance this is related to this patch?

Oops indeed; fixed in 36f18626a9f8e9ba287e0fd3f1d0400345ca5ee7.

It’s not ‘petsc’ that was affected but rather its variants; they’d lead
to a different derivation every time (!), one that fails to build:

  $ ./pre-inst-env guix build -d petsc-openmpi
  /gnu/store/lszhaiiyrkbdlldp42hqfhmaxcvqpfq7-petsc-openmpi-3.16.1.drv
  $ ./pre-inst-env guix build -d petsc-openmpi
  /gnu/store/r2gam9iwv67qvx8hq9sj9rj430qwa31c-petsc-openmpi-3.16.1.drv
  $ ./pre-inst-env guix build -d petsc-openmpi
  /gnu/store/iw7jkd9dqsfxiz8qij53wdhqg9xzgi5g-petsc-openmpi-3.16.1.drv

Fun.  :-)

Ludo’.


      reply	other threads:[~2021-12-01 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211128230450.9975.33919@vcs0.savannah.gnu.org>
     [not found] ` <20211128230453.64BA620B2A@vcs0.savannah.gnu.org>
2021-12-01 13:08   ` 04/05: gnu: petsc: Update to 3.16.1 Mathieu Othacehe
2021-12-01 22:33     ` Ludovic Courtès [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=875ys8ymzd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).