On Mon, Apr 08, 2013 at 09:17:48AM -0400, Jordi Gutiérrez Hermoso wrote:
On 4 April 2013 19:54, Bradley M. Froehle brad.froe...@gmail.com wrote:
If only there was a way for the different variants of HDF5 to be
simultaneously installable…
I think this is the real problem,and it goes way up
On 4 April 2013 19:54, Bradley M. Froehle brad.froe...@gmail.com wrote:
If only there was a way for the different variants of HDF5 to be
simultaneously installable…
I think this is the real problem,and it goes way up to HDF5 upstream.
They basically ship two completely different libraries with
Add HDF5 upstream contact address.
On 08/04/2013 15:17, Jordi Gutiérrez Hermoso wrote:
On 4 April 2013 19:54, Bradley M. Froehle brad.froe...@gmail.com wrote:
If only there was a way for the different variants of HDF5 to be
simultaneously installable…
I think this is the real problem,and
Hello All,
You should not have to install multiple HDF5 libraries. You can use the
same library for parallel or serial use, which is why it works the way
it does.
Can you give us more information on why you would like to have the
parallel library renamed?
Thanks,
-Barbara
On Sun, Mar 31, 2013 at 05:52:03PM -0700, Bradley M. Froehle wrote:
As an example of how confounding this is, just consider a simple example:
$ cat test.cpp
#include hdf5.h
#include mpi.h
int main() {
MPI::Init();
printf(I'm %d of %d\n, MPI::COMM_WORLD.Get_rank(),
More practically, and more importantly, Octave users who are compiling
extensions from within Octave are yet another step removed from both the
compiler and the HDF5 library. They may not even be aware of HDF5 but
the compilation and linking of their oct-file will be affected.
Mkoctfile
CC'ing pkg-octave-devel since this impacts Octave packaging as well.
Bradley M. Froehle wrote:
The fix for this bug provided in 1.8.9-1~exp2 has cause me a good deal of
headache today.
For me, the issue is triggered as some C++ code containing:
#include hdf5.h // sets OMPI_SKIP_MPICXX 1
Hi Mike:
Sorry that you'll get this twice. The first time around I accidentally
replied only to you. Please read on for responses inline.
On Sun, Mar 31, 2013 at 4:08 PM, Mike Miller mtmil...@ieee.org wrote:
CC'ing pkg-octave-devel since this impacts Octave packaging as well.
Thanks.
I've looked into this bug a bit today and I'd suggest that instead the
`mkoctfile-mpi.diff` patch in src:octave (from bug #598227) be modified to
be something more like:
-: ${XTRA_CXXFLAGS=%OCTAVE_CONF_XTRA_CXXFLAGS%}
+: ${XTRA_CXXFLAGS=-I/usr/include/mpi -DOMPI_SKIP_MPICXX=1
The fix for this bug provided in 1.8.9-1~exp2 has cause me a good deal of
headache today.
For me, the issue is triggered as some C++ code containing:
#include hdf5.h // sets OMPI_SKIP_MPICXX 1
#include mpi.h // MPI C++ namespace now is NOT available
Note that even trying to unset
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
Processing commands for cont...@bugs.debian.org:
reassign 686926 src:hdf5 1.8.8-9
Bug #686926 [liboctave-dev] liboctave-dev: creates broken .oct files when the
OpenMPI flavor of HDF5 (libhdf5-openmpi-dev) is installed
Bug reassigned from package 'liboctave-dev' to 'src:hdf5'.
Ignoring request
12 matches
Mail list logo
