From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27850-done@debbugs.gnu.org
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Date: Fri, 01 Sep 2017 11:35:23 +0100 [thread overview]
Message-ID: <87k21izoyc.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <87r2w2j7eb.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Wed, 23 Aug 2017 23:34:04 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Dave Love <fx@gnu.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>>> I went ahead and applied the patch you posted, minus the extra outputs,
>>
>> What's the problem with a runtime output?
>
> It’s mostly that this should be a separate patch, as discussed earlier.
OK. I've lost track, sorry. I'll have another look.
> It’s not a problem per se as long as it does help reduce the size of
> what people commonly install, which is not obvious to me.
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.
next prev parent reply other threads:[~2017-09-01 10:36 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 [this message]
2017-09-01 22:10 ` Ludovic Courtès
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
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=87k21izoyc.fsf@albion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=27850-done@debbugs.gnu.org \
--cc=ludo@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).