Package Details: mingw-w64-hdf5 1.14.4.3-2

Git Clone URL: https://aur.archlinux.org/mingw-w64-hdf5.git (read-only, click to copy)
Package Base: mingw-w64-hdf5
Description: General purpose library and file format for storing scientific data (mingw-w64)
Upstream URL: http://www.hdfgroup.org/HDF5/
Licenses: custom
Submitter: xantares
Maintainer: xantares
Last Packager: xantares
Votes: 1
Popularity: 0.000000
First Submitted: 2013-11-21 21:44 (UTC)
Last Updated: 2024-08-01 13:49 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Martchus commented on 2022-05-31 21:07 (UTC)

I'm getting a CMake error with the latest version:

CMake Warning at config/cmake/HDF5UseFortran.cmake:337 (message):


            Fortran REAL(KIND=0050:err:winediag:nodrv_CreateWindow L"The explorer process failed to start.") is $max_real_fortran_sizeof Bytes, but no corresponding C float type exists of that size
                                             !!! Fortran interfaces will not be generated for REAL(KIND=0050:err:winediag:nodrv_CreateWindow L"The explorer process failed to start.") !!!
Call Stack (most recent call first):
  CMakeLists.txt:1069 (include)


CMake Error at config/cmake/HDF5UseFortran.cmake:342 (math):
  math cannot parse the expression: "4,8,10,16 - 1": syntax error, unexpected
  exp_NUMBER, expecting end of file (4).
Call Stack (most recent call first):
  CMakeLists.txt:1069 (include

metroid120 commented on 2021-11-16 16:40 (UTC)

Can you please add: -DHDF5_BUILD_FORTRAN=ON \ ?

srtlg commented on 2021-10-11 10:51 (UTC)

From 1.12.0-2 to 1.12.1-1 support for C++ has been removed. Could you please add

--- PKGBUILD?h=mingw-w64-hdf5   2021-10-11 12:50:49.000000000 +0200
+++ PKGBUILD    2021-10-11 12:16:46.139345645 +0200
@@ -33,6 +33,7 @@
     mkdir -p build-${_arch} && pushd build-${_arch}
     ${_arch}-cmake \
       -DHDF5_ENABLE_Z_LIB_SUPPORT=ON \
+      -DHDF5_BUILD_CPP_LIB=ON \
       -DBUILD_TESTING=OFF \
       -DHDF5_BUILD_TOOLS=OFF \
       -DHDF5_BUILD_EXAMPLES=OFF \

tuxsavvy commented on 2018-06-15 23:54 (UTC)

Line 59 of PKGBUILD is incorrect. Here is a patch to rectify that issue:

--- PKGBUILD.old        2018-06-16 09:52:43.000000000 +0000
+++ PKGBUILD            2018-06-16 09:23:50.263953815 +0000
@@ -56,7 +56,7 @@

 package() {
   for _arch in $_architectures; do
-    cd "$srcdir/hdf5-${_arch}/build-${_arch}"
+    cd "$srcdir/hdf5-${pkgver/_/-}/build-${_arch}"
     make DESTDIR="${pkgdir}" install
     rm "$pkgdir"/usr/${_arch}/share/{COPYING,*.txt}
     ${_arch}-strip --strip-unneeded "$pkgdir"/usr/${_arch}/bin/*.dll

ezacaria commented on 2017-09-29 05:14 (UTC)

Thanks for the further comments. I agree that it is simpler to do so, specially if you mention that there is further hassle in maintenance. I tried without wine and setting -DHDF5_BUILD_TOOLS=ON. This attempts (and fails) to generate H5lib_settings.c, but at first glance the problem seems to be that the mingw-cmake is used when building the H5make_libsettings file, which results in a windows binary (therefore needing the workaround of using wine). This happens in file src/hdf5-1.10.1/build-x86_64-w64-mingw32/src/CMakeFiles/hdf5-static.dir/build.make. If we, on the other hand, were to specify that these few files should be built with the regular Linux cmake, then wine would not be needed. I do not know enough of the cmake system to say if this is easy to do, and I have the feeling that it is more hassle than worth as you suggested earlier. Let us leave it for now :) Thanks again!

xantares commented on 2017-09-28 17:52 (UTC)

Its easier to just require wine for the try compile checks instead of setting each cmake results var because it's a pain to maintain as they may change between releases or 32/64 arch. HDF5_BUILD_TOOLS is already off, and I doubt it has an impact on runtime checks.

ezacaria commented on 2017-09-28 15:24 (UTC)

Thanks again, and sorry for taking so long to come back with some feedback. The szip package compiled without problems but I did not attempt to build/test if it works. The new hdf5 PKGBUILD, on the other hand, works and the zlib compression is also effective when used. One comment on requiring wine to build this package, though. It occurred to me that perhaps we can compile the configuration tools (such as src/H5make_libsettings.c, which is responsible to generate H5lib_settings.c in the source before the actual compilation). Have you ever tried using "DHDF5_BUILD_TOOLS" to avoid the calls to wine?

xantares commented on 2017-08-16 20:26 (UTC) (edited on 2017-08-16 20:31 (UTC) by xantares)

updated, could you check ezacaria? also added szip package if you want to enable it.

ezacaria commented on 2017-08-15 11:31 (UTC)

First off, thanks for the package! I noticed that compression is not enabled when building the package. Even if the data sets show compression in the headers, the compression ratio is always 1 to 1 and no space savings are achieved. This is easy to fix, though. I added the following to the PKGBUILD to force zlib support: -DHDF5_ENABLE_Z_LIB_SUPPORT=ON \ -DHDF5_ENABLE_SZIP_SUPPORT=OFF \ -DHDF5_ENABLE_SZIP_ENCODING=OFF \ The basic zlib compression works now, without further pre-requisites (mingw-w64-zlib is already there). I could not compile the szip library in the mingw64 (or get the installation to compile it on the fly), but the zlib is enough for my purposes and therefore I disabled szip support. I also used the same PKGBUILD with the newer version (https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.10/hdf5-1.10.1/src/hdf5-1.10.1.tar.bz2). I am not sure if all the fixes in prepare() apply verbatim, though.

xantares commented on 2015-06-02 19:57 (UTC)

updating to 1.8.15 leads to weird compile errors, but this can be used: cmake_args="-DCMAKE_BUILD_TYPE=Release \ -DHAVE_IOEO_EXITCODE=0 \ -DHDF5_PRINTF_LL_TEST_RUN=0 \ -DHDF5_PRINTF_LL_TEST_RUN__TRYRUN_OUTPUT= \ -DH5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN=0 \ -DH5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN__TRYRUN_OUTPUT= \ -DH5_LDOUBLE_TO_LONG_SPECIAL_RUN=1 \ -DH5_LDOUBLE_TO_LONG_SPECIAL_RUN__TRYRUN_OUTPUT= \ -DH5_LONG_TO_LDOUBLE_SPECIAL_RUN=1 \ -DH5_LONG_TO_LDOUBLE_SPECIAL_RUN__TRYRUN_OUTPUT= \ -DH5_LDOUBLE_TO_LLONG_ACCURATE_RUN=0 \ -DH5_LDOUBLE_TO_LLONG_ACCURATE_RUN__TRYRUN_OUTPUT= \ -DH5_LLONG_TO_LDOUBLE_CORRECT_RUN=0 \ -DH5_LLONG_TO_LDOUBLE_CORRECT_RUN__TRYRUN_OUTPUT= \ -DH5_NO_ALIGNMENT_RESTRICTIONS_RUN=0 \ -DH5_NO_ALIGNMENT_RESTRICTIONS_RUN__TRYRUN_OUTPUT="

« First ‹ Previous 1 2 3 Next › Last »