dolfin team mailing list archive

[Jesper Carlsson <jesperc0@xxxxxxxxx>]

Hi,

I have not added any cxx flags manually.

Best regards,
Jesper

On Mon, Feb 2, 2009 at 8:57 AM, Johannes Ring <johannr@xxxxxxxxx> wrote:

> On Mon, February 2, 2009 04:09, Jesper Carlsson wrote:
> > Hi again,
> >
> > Seems like the problem was some old mpich libraries. Uninstalled mpich
> and
> > kept Open MPI, and it found the right libraries.
>
> Good.
>
> > Compiling without pydolfin works fine (and the demos work fine on one
> > processor), but with pydolfin I get the following error:
> >
> > mpic++ -o dolfin/swig/cpp_wrap.os -c -Wall -pipe -ansi -Werror -DDEBUG -g
> > -DNDEBUG -O2 -DHAS_MPI=1 -DMPICH_IGNORE_CXX_SEEK
> > -DPACKAGE_VERSION=\"0.9.0\"
> > -DHAS_PETSC=1 -DHAS_SCOTCH=1 -DHAS_UMFPACK=1 -DHAS_GTS=1 -DHAS_TRILINOS=1
> > -DHAS_CHOLMOD=1 -DHAS_PARMETIS=1 -fno-strict-aliasing -fPIC -I.
> > -I/usr/include -I/usr/include -I/usr/include/libxml2
> > -I/usr/lib/petscdir/2.3.3/bmake/linux-gnu-c-opt
> > -I/usr/lib/petscdir/2.3.3/include -I/usr/lib/openmpi/include
> > -I/usr/lib/openmpi/lib -Idolfin -I/usr/include/scotch
> > -I/usr/include/suitesparse -I/usr/include -I/usr/include/glib-2.0
> > -I/usr/lib/glib-2.0/include -I/usr/local/include
> > -I/usr/include/suitesparse
> > -I/usr/include -I/usr/include/python2.5 -I/usr/include/python2.5
> > -I/usr/lib/python2.5/site-packages/numpy/core/include -I/usr/include
> > -I/usr/include -I/usr/include/libxml2
> > -I/usr/lib/petscdir/2.3.3/bmake/linux-gnu-c-opt
> > -I/usr/lib/petscdir/2.3.3/include -I/usr/lib/openmpi/include
> > -I/usr/lib/openmpi/lib -Idolfin -I/usr/include/scotch
> > -I/usr/include/suitesparse -I/usr/include -I/usr/include/glib-2.0
> > -I/usr/lib/glib-2.0/include -I/usr/local/include
> > -I/usr/include/suitesparse
> > -I/usr/include dolfin/swig/cpp_wrap.cc
> > cc1plus: warnings being treated as errors
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> > _wrap_new_LUSolver(PyObject*, PyObject*)":
> > dolfin/swig/cpp_wrap.cc:57621: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject* _wrap_summary(PyObject*,
> > PyObject*)":
> > dolfin/swig/cpp_wrap.cc:30721: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> > _wrap_new_TimeDependent(PyObject*, PyObject*)":
> > dolfin/swig/cpp_wrap.cc:28678: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> > _wrap_new_uBLASVector(PyObject*, PyObject*)":
> > dolfin/swig/cpp_wrap.cc:42865: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> > _wrap_new_Vector(PyObject*,
> > PyObject*)":
> > dolfin/swig/cpp_wrap.cc:52979: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> _wrap_new_Table(PyObject*,
> > PyObject*)":
> > dolfin/swig/cpp_wrap.cc:31798: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
> > dolfin/swig/cpp_wrap.cc: In function "PyObject*
> > _wrap_new_DiscreteFunction(PyObject*, PyObject*)":
> > dolfin/swig/cpp_wrap.cc:68434: fel: "argv[0]" kan användas oinitierad i
> > denna funktion
>
> I wonder why -Werror is specified when compiling the SWIG wrapper code.
> This flag should have been removed at that stage. Have you defined
> CXXFLAGS manually or added this flag somewhere?
>
> Johannes
>
>
>
>