Bug 209980

Summary: patch: fix science/hdf5, API break from 1.8 to 1.10
Product: Ports & Packages Reporter: Kurt Jaeger <pi>
Component: Individual Port(s)Assignee: Po-Chuan Hsieh <sunpoet>
Status: Closed Overcome By Events    
Severity: Affects Only Me CC: thierry, truckman
Priority: --- Keywords: patch
Version: Latest   
Hardware: Any   
OS: Any   
Bug Depends on:    
Bug Blocks: 209242, 209244    
Attachments:
Description Flags
patch none

Description Kurt Jaeger freebsd_committer freebsd_triage 2016-06-02 19:13:56 UTC 
Created attachment 170958 [details]
patch

See

http://lists.freebsd.org/pipermail/freebsd-ports/2016-May/103358.html

The recent update from hdf5 1.8.16 to 1.10.0 has introduced
an issue with ABI incompatibility.  Thus, anyone that has
code written to the 1.8.16 ABI may find that their code no
longer functions with 1.10.0.  This should have been noted
in ports/UPDATING.

with patch from Steve Kargl <sgk@troutmask.apl.washington.edu>, see attachment
Comment 1 Thierry Thomas freebsd_committer freebsd_triage 2016-06-02 19:26:59 UTC 
Could you please explain how it has been fixed?
Thanks
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2016-06-02 19:38:12 UTC 
The two ports reported as broken are fixed, their tickets closed,
so I assume the patch is no longer necessary.

If it's still necessary, please reopen.
Comment 3 Thierry Thomas freebsd_committer freebsd_triage 2016-06-02 20:42:23 UTC 
The 2 broken dependent ports have been fixed locally, but the general case (particularly for FORTRAN consumers) is not yet fixed.

See the thread beginning at https://docs.freebsd.org/cgi/getmsg.cgi?fetch=65714+0+current/freebsd-ports
Comment 4 Thierry Thomas freebsd_committer freebsd_triage 2016-06-02 20:43:45 UTC 
Assign to maintainer.
Comment 5 Don Lewis freebsd_committer freebsd_triage 2016-06-02 21:38:34 UTC 
(In reply to Thierry Thomas from comment #3)

Fixes were committed for matio and scilab.  They now explicitly specify that they want to use the version 1.8 API.  Portmon reports that they are now successfully building.

There are a number of other consumers of hdf5.  I don't know their status.

Consumers written in C can specify the API version that they want with CPPFLAGS.
Fortran consumers are more of a concern.  Changing the default API version helps in the short term, but what happens when ports start wanting to use conflicting API versions of the fortran modules?
Comment 6 Thierry Thomas freebsd_committer freebsd_triage 2016-06-03 20:17:19 UTC 
Unfortunately, this is often a problem with HDF: I remember that some years ago, Code_Aster's upstream had to deal with H5_USE_16_API with hdf5-18.

We already have science/hdf and science/hdf5, and at some point we might need 2 un-conflicting ports for hdf5... Meanwhile, it would be better to respect the 1.8 API.
Comment 7 Po-Chuan Hsieh freebsd_committer freebsd_triage 2016-11-17 17:23:23 UTC 
science/hdf5-18 has been resurrected.