all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Eric Bavier <bavier@posteo.net>
Cc: "Franck Pérignon" <Franck.Perignon@univ-grenoble-alpes.fr>,
	"Eric Bavier" <bavier@member.fsf.org>,
	47619@debbugs.gnu.org, "Leo Famulari" <leo@famulari.name>
Subject: [bug#47619] [PATCH] add pt-scotch-shared/scotch-shared
Date: Sat, 10 Apr 2021 11:59:48 +0200	[thread overview]
Message-ID: <878s5q31ez.fsf@gnu.org> (raw)
In-Reply-To: <db52ab439fed6f1e76ca8b921b461a3964af3f9b.camel@posteo.net> (Eric Bavier's message of "Fri, 09 Apr 2021 22:24:26 -0500")

Hi,

Eric Bavier <bavier@posteo.net> skribis:

> On Thu, 2021-04-08 at 09:21 +0200, Ludovic Courtès wrote:
>> Hello,
>> I was wondering whether we should provide exclusively shared libraries,
>> as we do for other packages, instead of keeping ‘scotch’ and
>> ‘scotch-shared’.  Thoughts?
>
> I know in the past many in the HPC realm have wanted to have static
> libraries available, to avoid the costs associated with start-up
> linking and global function table indirection.
>
> Some current developments, such as some HPC system vendors moving to
> support only shared libraries on future systems, suggests that this
> preference might be waning.

Yeah, I doubt this preference is justified, I feel it’s more one of
these cultural things.  But yeah, let’s keep both for now.

Would it make sense to rename “scotch” to “scotch-static” and
“scotch-shared” to “scotch”, for consistency?

Ludo’.




      reply	other threads:[~2021-04-10 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 11:22 [bug#47619] [PATCH] add pt-scotch-shared/scotch-shared Franck Pérignon
2021-04-06 17:54 ` bug#47619: " Leo Famulari
2021-04-08  7:21 ` [bug#47619] " Ludovic Courtès
2021-04-10  3:24   ` Eric Bavier
2021-04-10  9:59     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s5q31ez.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47619@debbugs.gnu.org \
    --cc=Franck.Perignon@univ-grenoble-alpes.fr \
    --cc=bavier@member.fsf.org \
    --cc=bavier@posteo.net \
    --cc=leo@famulari.name \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.