octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #38091] image-2.0.0 install failure on Ubuntu


From: anonymous
Subject: [Octave-bug-tracker] [bug #38091] image-2.0.0 install failure on Ubuntu 12.04 - diagnosed, outline fix
Date: Tue, 15 Jan 2013 08:49:03 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0

URL:
  <http://savannah.gnu.org/bugs/?38091>

                 Summary: image-2.0.0 install  failure on Ubuntu 12.04 -
diagnosed, outline fix
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 15 Jan 2013 08:49:02 UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Installation
                  Status: None
             Assigned to: None
         Originator Name: Ian Flintoft
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

image-2.0.0 fails to install in octave 3.6.4-rc1 compiled
from source on my Ubuntu 12.04 64-bit system.

Install log:


octave:1> pkg install -auto -verbose  image-2.0.0.tar.gz
mkdir (/tmp/oct-CberoK)
untar (image-2.0.0.tar.gz, /tmp/oct-CberoK)
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking unordered_map usability... yes
checking unordered_map presence... yes
checking for unordered_map... yes
checking whether unordered_map requires tr1 namespace... no
configure: creating ./config.status
config.status: creating config.h
In file included from /usr/include/hdf5.h:24:0,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/oct-hdf5.h:27,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/ov.h:43,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/oct-obj.h:34,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/ov-fcn.h:32,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/ov-builtin.h:28,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/defun-int.h:28,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/defun-dld.h:30,
                 from
/opt/octave-3.6.4-rc1/include/octave-3.6.4-rc1/octave/oct.h:36,
                 from bwlabeln.cc:20:
/usr/include/H5public.h:57:20: fatal error: mpi.h: No such file or directory
compilation terminated.
make: *** [bwlabeln.oct] Error 1


The CXXFLAGS prepended to the MKOCTFILE command in the 
Makefile


bwlabeln.oct: bwlabeln.cc union-find.h++
        CXXFLAGS='-g -O2 -std=c++0x -Wall' $(MKOCTFILE) $<


appear to override those in /opt/octave-3.6.4-rc1/bin/mkoctfile:


: ${CXXFLAGS="-I/usr/include/openmpi"}


causing the failure.

Note: For Ubuntu 12.04 I had to compile octave with 
CXXFLAGS='-I/usr/include/openmpi' so that hdf5 can find the 
openmpi headers which are located in /usr/include/openmpi but 
included in the hdf5 file using "#include<mpi.h>". Adding
these flag to the image-2.0.0 Makefile line solve the
problem but the real fix is presumably to append any extra CXXFLAGS to those
defined in mkoctfile rather than overiding them?





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38091>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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