HDF5 Problem

[Adam Dershowitz]

This ticket is showing the same error, although the situation is slightly different, since it is using the older version that worked fine for me:
https://trac.macports.org/ticket/52289 <https://trac.macports.org/ticket/52289>


--Adam



> On Oct 13, 2016, at 12:07 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
>> On Oct 13, 2016, at 11:05 AM, Eric A. Borisch <eborisch at macports.org> wrote:
>> 
>> As the error message points out, you can set HDF5_DISABLE_VERSION_CHECK=1 (or 2) to make things run. As they say, don't blame them if it crashes.
>> 
>> There are plenty of reports out there (outside of MP) on this HDF5 feature. As far as I can tell, the HDF5 group's position is that they are used for storing critical data (output from experiments that you don't want to have to "re-do"), so they don't ever want to be the cause of errors from unintentional / unexpected behavior, even if the program can happily link.
>> 
>> It would be nice if we had some centralized way to handle this rather than rev-bumping each dependent port, but that is where we are currently at. Is it possible to have an hdf5 PortGroup where we could centrally bump an epoch?
> 
> No; bumping the epoch is not sufficient; you must change the revision or version for MacPorts to see it as an upgrade.
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20161014/5367b0bc/attachment-0002.html>