From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 27850-done@debbugs.gnu.org
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Date: Sat, 02 Sep 2017 00:10:24 +0200 [thread overview]
Message-ID: <87h8wmysrz.fsf@gnu.org> (raw)
In-Reply-To: <87k21izoyc.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Fri, 01 Sep 2017 11:35:23 +0100")
Heya,
Dave Love <fx@gnu.org> skribis:
> I'm afraid I don't know about "commonly", particularly with Guix, but
> I'm surprised if people would expect to get the respective MPI
> development environment for an MPI program they install any more than
> they'd expect the compiler generally. The separation other
> distributions have seems appropriate to me as a system manager and
> packager -- even if it's not the typical HPC way (Spack et al?) -- but
> that's just my opinion.
As I wrote before, Guix currently doesn’t have as fine grain a
separation as Debian, Fedora, & co.: we add an extra output when we have
evidence that it provides noticeably space savings.
We could discuss that policy of course, but that’s another story.
Ludo’.
next prev parent reply other threads:[~2017-09-01 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 15:01 [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple Dave Love
2017-07-31 15:16 ` Ludovic Courtès
2017-07-31 18:09 ` Dave Love
2017-08-01 9:27 ` Ludovic Courtès
2017-08-01 16:06 ` Dave Love
2017-08-01 17:39 ` Ludovic Courtès
2017-08-01 20:10 ` Dave Love
2017-08-21 13:17 ` bug#27850: " Ludovic Courtès
2017-08-23 11:08 ` [bug#27850] " Dave Love
2017-08-23 21:34 ` Ludovic Courtès
2017-09-01 10:35 ` Dave Love
2017-09-01 22:10 ` Ludovic Courtès [this message]
2017-09-07 16:16 ` Dave Love
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=87h8wmysrz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27850-done@debbugs.gnu.org \
--cc=fx@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 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.