Bug#686926: [Pkg-octave-devel] Bug#686926: Bug#686926: liboctave-dev: creates broken .oct files when the OpenMPI flavor of HDF5 (libhdf5-openmpi-dev) is installed
On Fri, Sep 07, 2012 at 09:11:34AM -0400, Mike Miller wrote: mkoctfile -DMPICH_SKIP_MPICXX=1 -DOMPI_SKIP_MPICXX=1 helloworld.cc I don't know enough about HDF5, but if it doesn't make use of the MPI C++ bindings at all, I'd argue this should be reassigned to hdf5 upstream so H5public.h would now contain: #ifdef H5_HAVE_PARALLEL # define MPICH_SKIP_MPICXX 1 # define OMPI_SKIP_MPICXX 1 # include mpi.h #endif Is my understanding correct that if I want to use HDF5 and one of MPICH or MPI with the C++ interface, I have lost? Thoma -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686926: [Pkg-octave-devel] Bug#686926: Bug#686926: liboctave-dev: creates broken .oct files when the OpenMPI flavor of HDF5 (libhdf5-openmpi-dev) is installed
On Mon, Sep 10, 2012 at 2:46 PM, Thomas Weber wrote: On Fri, Sep 07, 2012 at 09:11:34AM -0400, Mike Miller wrote: mkoctfile -DMPICH_SKIP_MPICXX=1 -DOMPI_SKIP_MPICXX=1 helloworld.cc I don't know enough about HDF5, but if it doesn't make use of the MPI C++ bindings at all, I'd argue this should be reassigned to hdf5 upstream so H5public.h would now contain: #ifdef H5_HAVE_PARALLEL # define MPICH_SKIP_MPICXX 1 # define OMPI_SKIP_MPICXX 1 # include mpi.h #endif Is my understanding correct that if I want to use HDF5 and one of MPICH or MPI with the C++ interface, I have lost? Could be, I hadn't thought through all the unintended consequences yet. On the flip side, the way it is now if I want to compile C++ with just HDF5, I have to link in libraries that I don't really need. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
