Summary: | sci-libs/hdf5-1.6.2 (and 1.6.4) cannot build because of Bus error in H5detect | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ferris McCormick (RETIRED) <fmccor> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | sparc |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | Sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 371525 |
Description
Ferris McCormick (RETIRED)
![]() Actually, the failure is in detect_C89_integers(void) when trying to do this: DETECT_I(short, SHORT, d_g[nd_g]); nd_g++; Apparently, this fails: ALIGNMENT(TYPE, INFO); where TYPE=short, INFO=d_g[2] but further decoding the ALIGNMENT macro is beyond me right now. Considered reporting this upstream, Ferris? How's 1.6.5 on sparc? Seems to do good, but if you build it without the static USE h5cc will still keep looking for the static lib unless you use HDF5_USE_SHLIB=yes (thank Ferris for finding out). Should this be documented in some way? Fixed by hdf5-1.6.5, adding ~sparc keyword and closing the bug. NOTE: 1) FEATURES='test' USE='static' emerge hdf5 runs all tests and installs; h5cc works as expected. 2) FEATURES='test' USE='mpi' emerge hdf5 FAILS because lam-mpi will not run as root; 3) USE='mpi; emerge hdf5 works fine. 4) Please note Comment #4 --- if you do not build with USE=static, to use h5cc, you must set HDF5_USE_SHLIB="yes". This used to be documented in h5cc --help, but no longer is. However, it still seems to be the case. I have a version of the 1.6.5 ebuild that runs all the tests, including the mpi tests (it runs mpd as portage; tested with mpich2 so far). However, it still uses the HDF5_Make_Ignore=yes flag to make it through the tests (one set of mpi tests still fails, but all the MPIPOSIX and other tests complete successfully). I still need to try another mpi package, as well as track down exactly what causes the failure (I'm also having weird failures on the build of the mpich2 test drivers, but only 6 tests failed out of 373). And those tests take a while, even on a fast machine... |