h5py 1.2 and api=18
37 views
Skip to first unread message
Art
Jun 5, 2009, 5:14:25 PM6/5/09
to h5py
Dear Andrew,
Does version 1.2 work with api=18? I tried it and I still got -
DH5_USE_16_API flags in the build. I changed setup.py to force api=18
and I got some errors (probably shouldn't have made those changes):
gcc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-
aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -
dynamic -DNDEBUG -g -O3 -I/tmp/_py/libraries/usr/local/include -I/
Library/Frameworks/Python.framework/Versions/4.3.0/lib/python2.5/site-
packages/numpy-1.3.0n1-py2.5-macosx-10.3-fat.egg/numpy/core/include -I/
usr/local/hdf5/include -I/Users/amir/Build/py/h5py-1.2.0-beta/lzf -I/
Library/Frameworks/Python.framework/Versions/4.3.0/include/python2.5 -
c h5py/h5e.c -o build/temp.macosx-10.3-fat-2.5/h5py/h5e.o -
DH5_USE_18_API -Wno-unused -Wno-uninitialized
h5py/h5e.c: In function ‘__pyx_pf_4h5py_3h5e_10ErrorStack___init__’:
h5py/h5e.c:1241: error: incompatible type for argument 2 of ‘H5Ewalk2’
h5py/h5e.c:1241: error: too few arguments to function ‘H5Ewalk2’
h5py/h5e.c: In function ‘__pyx_f_4h5py_3h5e_register_thread’:
h5py/h5e.c:2148: warning: passing argument 1 of ‘H5Eset_auto2’ makes
integer from pointer without a cast
h5py/h5e.c:2148: error: too few arguments to function ‘H5Eset_auto2’
Your new features sound great. Can't wait to use them.
Art
Does version 1.2 work with api=18? I tried it and I still got -
DH5_USE_16_API flags in the build. I changed setup.py to force api=18
and I got some errors (probably shouldn't have made those changes):
gcc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-
aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -
dynamic -DNDEBUG -g -O3 -I/tmp/_py/libraries/usr/local/include -I/
Library/Frameworks/Python.framework/Versions/4.3.0/lib/python2.5/site-
packages/numpy-1.3.0n1-py2.5-macosx-10.3-fat.egg/numpy/core/include -I/
usr/local/hdf5/include -I/Users/amir/Build/py/h5py-1.2.0-beta/lzf -I/
Library/Frameworks/Python.framework/Versions/4.3.0/include/python2.5 -
c h5py/h5e.c -o build/temp.macosx-10.3-fat-2.5/h5py/h5e.o -
DH5_USE_18_API -Wno-unused -Wno-uninitialized
h5py/h5e.c: In function ‘__pyx_pf_4h5py_3h5e_10ErrorStack___init__’:
h5py/h5e.c:1241: error: incompatible type for argument 2 of ‘H5Ewalk2’
h5py/h5e.c:1241: error: too few arguments to function ‘H5Ewalk2’
h5py/h5e.c: In function ‘__pyx_f_4h5py_3h5e_register_thread’:
h5py/h5e.c:2148: warning: passing argument 1 of ‘H5Eset_auto2’ makes
integer from pointer without a cast
h5py/h5e.c:2148: error: too few arguments to function ‘H5Eset_auto2’
Your new features sound great. Can't wait to use them.
Art
Art
Jun 5, 2009, 5:30:57 PM6/5/09
to h5py
Sorry, my mistake. The new Enthought EPD (4.3) has it's own hdf5
library and it was getting linked before mine (they have 1.8.1, I have
1.8.2) so things were breaking, not because of h5py. After removing
the Enthought libraries, problem is fixed and all tests run fine.
Should I ignore the DH5_USE_16_API flags?
library and it was getting linked before mine (they have 1.8.1, I have
1.8.2) so things were breaking, not because of h5py. After removing
the Enthought libraries, problem is fixed and all tests run fine.
Should I ignore the DH5_USE_16_API flags?
Andrew Collette
Jun 5, 2009, 5:33:16 PM6/5/09
to h5...@googlegroups.com
Hi Art,
> Sorry, my mistake. The new Enthought EPD (4.3) has it's own hdf5
> library and it was getting linked before mine (they have 1.8.1, I have
> 1.8.2) so things were breaking, not because of h5py. After removing
> the Enthought libraries, problem is fixed and all tests run fine.
> Should I ignore the DH5_USE_16_API flags?
Yes, this flag is just a compatibility setting for HDF5 1.8. You'll
still have access to all the new 1.8 features.
Glad it works!
Andrew
Reply all
Reply to author
Forward
0 new messages