unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Gerd Heber <gerd.heber@gmail.com>
Cc: David Elsing <david.elsing@posteo.net>,
	bavier@posteo.net, 64448@debbugs.gnu.org, efraim@flashner.co.il
Subject: [bug#64448] [PATCH 0/2] Fix hdf5-1.14 wrappers and remove generated source files from all hdf5 versions.
Date: Mon, 21 Aug 2023 22:24:36 +0200	[thread overview]
Message-ID: <ZOPIBKX-2EHyiIAB@jurong> (raw)
In-Reply-To: <CANnLdWG=1CBdb4FEKoo-xS_Y3=eGp7hMjterixz_KA6s73CDXA@mail.gmail.com>

Am Sun, Aug 20, 2023 at 07:36:50PM -0500 schrieb Gerd Heber:
> Only HDF5 1.14.x (currently, 1.14.2) should be kept. However, hdf5 and
> hdf5-parallel should be kept separate. Aside from the MPI dependence,
> the parallel build is NOT a superset of the sequential version. There could be
> even two versions of hdf5: a non-threadsafe build (hdf5) and a threadsafe build
> (hdf5-ts? hdf5-mt?).
> 
> For HDF4, 4.2.16-2 is the latest HDF4 release. We are maintaining that
> indefinitely (for NASA).

Thanks for the info, which helps us set a target!

I am trying to update hdf4, see
   https://issues.guix.gnu.org/65443

Andreas





  reply	other threads:[~2023-08-21 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 21:58 [bug#64448] [PATCH 0/2] Fix hdf5-1.14 wrappers and remove generated source files from all hdf5 versions David Elsing
2023-07-03 22:00 ` [bug#64448] [PATCH 1/2] gnu: hdf5-1.8: Remove generated files from source David Elsing
2023-07-03 22:00 ` [bug#64448] [PATCH 2/2] gnu: hdf5-1.14: Remove spurious include directories David Elsing
2023-07-04 21:14 ` [bug#64448] [PATCH 0/2] Fix hdf5-1.14 wrappers and remove generated source files from all hdf5 versions David Elsing
2023-07-24 13:49 ` Andreas Enge
2023-07-24 14:00   ` Andreas Enge
2023-09-25 22:06     ` David Elsing
2023-08-21  0:36   ` Gerd Heber
2023-08-21 20:24     ` Andreas Enge [this message]
2023-08-21 20:38       ` Andreas Enge

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=ZOPIBKX-2EHyiIAB@jurong \
    --to=andreas@enge.fr \
    --cc=64448@debbugs.gnu.org \
    --cc=bavier@posteo.net \
    --cc=david.elsing@posteo.net \
    --cc=efraim@flashner.co.il \
    --cc=gerd.heber@gmail.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 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).