On Mon, Jun 13, 2016 at 09:36:59AM -0000, Einstein Toolkit wrote:
#1910: ExternalLibraries/HDF5 does not set HDF5_INC_DIRS ----------------------------+----------------------------------------------- Reporter: barry.wardell | Owner: eschnett Type: defect | Status: assigned Priority: unset | Milestone: Component: Other | Version: development version Resolution: | Keywords: ----------------------------+-----------------------------------------------
Comment (by knarf):
Looking at this, HDF5_INC_DIRS should be set by bash_utils.sh (assuming you set HDF5_DIR, but none of the other variables in your option list).
Can you please attach details about your setup, in particular:
- How is your hdf5 library installed (which INC_DIRS, LIB_DIRS, LIBS would
be correct)?
- Your option list
- The output of detect.sh, when called by Cactus as part of a build
I plan to create release branches in about 8 hours (or so). It would be splendid if this could be fixed until then. If not, it will need to be fixed on both trunk and the release branch, until tomorrow at about the time of this email. If it isn't 'in' until then, it will not be part of the initial release, but would be a prime candidate for a fix later.
Current plan for action is release on Wednesday. I will not treat this as blocker for the reason that this is unlikely to affect most users, and the ones that are affected are not unlikely to be experienced enough to find a workaround.
Frank
On Mon, Jun 13, 2016 at 11:53:09AM +0200, Frank Loeffler wrote:
I plan to create release branches in about 8 hours (or so).
That plan literally was rained on, so expect this some time this morning.
Frank
Hi
On Tue, Jun 14, 2016 at 08:06:23AM +0200, Frank Loeffler wrote:
I plan to create release branches in about 8 hours (or so).
The release branches have been created, and you can use the following URL to get a checkout of it (remember, GetComponents also takes URLs):
https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2016_05/einsteintoolki...
This does NOT mean the release it out of the door yet.
If we don't see any errors, this will be what will be released, hopefully soon. The more errors we can detect now the better. Critical things would still be fixed, non-critical can be mentioned in the release notes. In order for any of this to happen, we need
* YOU *
to test the to-be release.
Frank
users@lists.einsteintoolkit.org