octave-maintainers
[Top][All Lists]
Advanced

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

Re: Error installing package on classdef tip


From: Mike Miller
Subject: Re: Error installing package on classdef tip
Date: Wed, 23 Oct 2013 08:53:44 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Oct 23, 2013 at 10:44:32 +0100, Richard Crozier wrote:
> On 23/10/2013 10:32, Richard Crozier wrote:
> >
> >
> >I'm using hg id e2ed1c0ac403 (classdef) tip
> >
> >
> 
> I manually added #include <string> to version.h

FYI this was fixed on default but probably not yet merged to classdef.

  http://hg.savannah.gnu.org/hgweb/octave/rev/3d862202c4f6

> now I get
> 
> >> pkg install odepkg -forge
> In file included from /usr/include/hdf5.h:24:0,
>                  from
> /usr/local/include/octave-3.7.7+/octave/oct-hdf5.h:27,
>                  from /usr/local/include/octave-3.7.7+/octave/ov.h:42,
>                  from /usr/local/include/octave-3.7.7+/octave/oct-obj.h:34,
>                  from /usr/local/include/octave-3.7.7+/octave/ov-fcn.h:32,
>                  from
> /usr/local/include/octave-3.7.7+/octave/ov-builtin.h:28,
>                  from
> /usr/local/include/octave-3.7.7+/octave/defun-int.h:28,
>                  from
> /usr/local/include/octave-3.7.7+/octave/defun-dld.h:30,
>                  from /usr/local/include/octave-3.7.7+/octave/oct.h:36,
>                  from odepkg_octsolver_mebdfdae.cc:43:
> /usr/include/H5public.h:63:20: fatal error: mpi.h: No such file or directory

Yeah, this means you have one of the MPI-enabled versions of HDF5
installed. On Debian/Ubuntu these packages are libhdf5-mpich2-dev and
libhdf5-openmpi-dev. I recommend installing the non-MPI library,
libhdf5-dev (or libhdf5-serial-dev if you're on LTS or other old
release) and this problem will go away. If you can't or want to keep the
packages you have, you'll have to add the appropriate compiler flags to
build with the MPI headers.

I have used

  CPPFLAGS="-I/usr/include/mpi -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX"

with success when building Octave. If you build Octave this way, those
flags are saved in the defaults for mkoctfile passed to all subsequent
oct-file builds. Otherwise, for building a package as you are, I think
you can add that to your environment and mkoctfile will pick it up. It
should not need to be something you add to the makefile for odepkg.

HTH,

-- 
mike


reply via email to

[Prev in Thread] Current Thread [Next in Thread]