[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [DebianGIS] Package of hdf-1.8.3, first try



On Thu, Jun 18, 2009 at 10:44:58AM +0200, Heiko Klein wrote:
> Hi,
> 
> I'm eager to build a debian/ubuntu package of netcdf4 which requires
> hdf-1.8.3. I've seen that it is on the todo list of this group, but
> without explicit roadmap, so I gave it a try to build a
> hdf5-package:
> 
> http://pastebin.met.no/pastebin/cgi-bin/file?id=afbf25c4b95a64a3ecf0e97ca4b713731f08f589/hdf5_1.8.3.orig.tar.gz
> http://pastebin.met.no/pastebin/cgi-bin/file?id=4e69a51659c8fa467ed66534b0e5105d2209a1d9/hdf5_1.8.3-1.diff.gz

Interestingly enough the configure.in of 1.8.3 has some bugs and
currently openmpi on i386 has some issues with HDF5...

...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles...
no
checking build system type... i486-pc-linux-gnu
checking host system type... i486-pc-linux-gnu
checking shell variables initial values... done
checking if basename works... yes
checking if xargs works... yes
checking for cached host... none
checking for config i486-pc-linux-gnu... no
checking for config i486-pc-linux-gnu... no
checking for config pc-linux-gnu... no
checking for config pc-linux-gnu... no
checking for config i486-linux-gnu... no
checking for config i486-linux-gnu... no
checking for config i486-pc... no
checking for config linux-gnu... found
../../config/linux-gnulibc1: line 59: 13019 Segmentation fault      $FC
-V > $tmpfile
checking for config ../../config/site-specific/host-klecker... no
checking for i486-linux-gnu-gcc... mpicc.openmpi
checking for C compiler default output file name... 
configure: error: in
`/users/frankie/debian/debian-gis/supported/hdf5/hdf5-1.8.2/debian/build-openmpi':
configure: error: C compiler cannot create executables
See `config.log' for more details.



-- 
Francesco P. Lovergine



Reply to: