[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
From: |
Dave Love |
Subject: |
[bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple |
Date: |
Thu, 07 Sep 2017 17:16:58 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Ludovic Courtès <address@hidden> writes:
> Heya,
>
> Dave Love <address@hidden> 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.
Sorry again, I'd forgotten, with holiday breaks and things, about the
dependency on gfortran being removed. (I'm not sure that's a good idea,
since the library is version-specific.) Since I've expurgated the
contribution to the closure from valgrind it looks a lot better.
Keeping a dependency on gfortran I think would only contribute the
"self" of gfortran. That's actually a lot smaller than libgfortran,
which has a load of stuff that presumably shouldn't be in it, like
libstdc++ and the sanitizer support.
> We could discuss that policy of course, but that’s another story.
>
> Ludo’.