--- Begin Message ---
Subject: |
[PATCH 0/2] Build a thread-safe hdf5 library |
Date: |
Fri, 10 May 2019 11:56:30 +0200 |
Hello!
A colleague of mine noticed that our ‘hdf5’ library wasn’t
thread-safe. Turns out there’s an option to make it thread-safe (oh!),
it’s turned off by default (oh?!), and when you pass it ‘configure’
invites you to turn off no less than C++, Fortran, and the high-level
interface (d’oh!).
It also tells you that, if you insist, you can go ahead and pass
‘--enable-unsupported’, but you’re on your own.
We found that Debian chose to pass ‘--enable-unsupported’, and indeed
that seems to be saner than providing a variant that does very little,
but does it in a thread-safe way.
Thoughts?
Thanks,
Ludo’.
Ludovic Courtès (2):
gnu: hdf5: Build a thread-safe library.
gnu: hdf5: Add dependency on Perl.
gnu/packages/maths.scm | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
--
2.21.0
--- End Message ---
--- Begin Message ---
Subject: |
Re: [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library |
Date: |
Tue, 14 May 2019 12:21:08 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Hi Paul,
Paul Garlick <address@hidden> skribis:
> I notice in the Debian rules file [1] that the "--enable-threadsafe"
> flag is listed as one of the SERIAL_FLAGS. In the Guix case the
> package hdf5-parallel-openmpi inherits its configure flags from the
> hdf5 (serial) package.
>
> Will we also have to explicitly delete the "--enable-threadsafe" flag
> from the hdf5-parallel-openmpi definition?
Good point, I think so.
I did that and pushed it as 549d15712fdc1f58ce0dd11117eb79535ec19f2c.
Let me know if anything is amiss!
Ludo’.
--- End Message ---