From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bavier@cray.com, 35666@debbugs.gnu.org,
pgarlick@tourbillion-technology.com
Subject: [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library
Date: Fri, 10 May 2019 13:52:42 +0200 [thread overview]
Message-ID: <87imuisf05.fsf@elephly.net> (raw)
In-Reply-To: <20190510095630.16695-1-ludo@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> 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!).
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.
What other effects does “--enable-unsupported” have? I see that in
Fedora “--enable-threadsafe” was removed in 2008 because it’s
“incompatible with --enable-cxx and --enable-fortran”.
Instead they seem to be building different flavours: one with
--enable-fortran, another with --enable-cxx, yet another with MPI and
--enable-parallel.
Do we have contact to the hdf5 developers to ask what the implications
of “enable-unsupported” are?
--
Ricardo
next prev parent reply other threads:[~2019-05-10 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:56 [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library Ludovic Courtès
2019-05-10 10:05 ` [bug#35666] [PATCH 1/2] gnu: hdf5: Build a thread-safe library Ludovic Courtès
2019-05-10 10:05 ` [bug#35666] [PATCH 2/2] gnu: hdf5: Add dependency on Perl Ludovic Courtès
2019-05-10 11:52 ` Ricardo Wurmus [this message]
2019-05-10 13:07 ` [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library Ludovic Courtès
2019-05-10 15:09 ` Eric Bavier
2019-05-14 7:28 ` Ludovic Courtès
2019-05-14 14:40 ` Eric Bavier
2019-05-10 15:27 ` Paul Garlick
2019-05-14 10:21 ` bug#35666: " Ludovic Courtès
2019-05-14 12:02 ` [bug#35666] " Ricardo Wurmus
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=87imuisf05.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35666@debbugs.gnu.org \
--cc=bavier@cray.com \
--cc=ludo@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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.