← Back to team overview

dolfin team mailing list archive

Re: [Instant-dev] Problems with caching of code

 



Kent-Andre Mardal wrote:
I get:

 mpicxx -DPACKAGE_NAME=\"DOLFIN\" -DPACKAGE_TARNAME=\"dolfin\"
-DPACKAGE_VERSION=\"0.7.1\" "-DPACKAGE_STRING=\"DOLFIN 0.7.1\""
-DPACKAGE_BUGREPORT=\"http://www.fenics.org/bugzilla/\"; -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DHAVE_BOOST= -I. -I/usr/include/python2.5 -I../../src/kernel/common
-I../../src/kernel/elements -I../../src/kernel/fem
-I../../src/kernel/function -I../../src/kernel/graph
-I../../src/kernel/io -I../../src/kernel/la -I../../src/kernel/main
-I../../src/kernel/math -I../../src/kernel/mesh -I../../src/kernel/mf
-I../../src/kernel/nls -I../../src/kernel/ode -I../../src/kernel/pde
-I../../src/kernel/quadrature -I../../src/kernel/parameter
-I../../src/kernel/log -I../../src/kernel/plot -I/usr/include
-I/usr/include/libxml2 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/local/include -I../../src/pydolfin
-I/usr/include/python2.5
-I/usr/lib/python2.5/site-packages/numpy/core/include -DNDEBUG -g -O2
-fno-strict-aliasing -Wall -Werror -ansi -Wno-uninitialized -MT
_dolfin_la-dolfin_wrap.lo -MD -MP -MF .deps/_dolfin_la-dolfin_wrap.Tpo
-c dolfin_wrap.cpp  -fPIC -DPIC -o .libs/_dolfin_la-dolfin_wrap.o
dolfin_wrap.cpp: In function 'PyObject* _wrap_new_Assembler(PyObject*,
PyObject*)':
dolfin_wrap.cpp:64884: error: no matching function for call to
'dolfin::Assembler::Assembler()'
../../src/kernel/fem/dolfin/Assembler.h:37: note: candidates are:
dolfin::Assembler::Assembler(dolfin::Mesh&)
../../src/kernel/fem/dolfin/Assembler.h:33: note:
dolfin::Assembler::Assembler(const dolfin::Assembler&)
dolfin_wrap.cpp: In function 'PyObject*
_wrap_Assembler_assemble__SWIG_0(PyObject*, PyObject*)':
dolfin_wrap.cpp:65010: error: no matching function for call to
'dolfin::Assembler::assemble(dolfin::GenericTensor&, const
dolfin::Form&, dolfin::Mesh&, bool&)'
../../src/kernel/fem/dolfin/Assembler.h:43: note: candidates are: void
dolfin::Assembler::assemble(dolfin::GenericTensor&, const dolfin::Form&,
bool)
../../src/kernel/fem/dolfin/Assembler.h:47: note:                 void
dolfin::Assembler::assemble(dolfin::GenericTensor&, const dolfin::Form&,
const dolfin::SubDomain&, bool)
../../src/kernel/fem/dolfin/Assembler.h:53: note:                 void
dolfin::Assembler::assemble(dolfin::GenericTensor&, const dolfin::Form&,
const dolfin

.....


Did you do

  touch src/pydolfin/dolfin.i

to force re-generation of the Python interface?

Garth



tir, 11.12.2007 kl. 13.40 +0000, skrev Garth N. Wells:
Kent-Andre Mardal wrote:
Strange, I will try to run your example, but currently I don't manage to
compile dolfin. I do ./configure --disable-mpi but still mpicxx is
used.
It should still compile ok. --disable-mpi sets a flag such that mpi-related code inside DOLFIN is not compiled.

Garth


man, 10.12.2007 kl. 21.35 +0100, skrev Anders Logg:
We still have problems in FFC when using the new feature for caching
generated code in Instant.

If I run the standard Poisson demo in DOLFIN (src/demo/pde/poisson/python)
then the first time Instant generates code and compiles it. Then if I
run again, the code gets reused as expected.

Now, if I remove the code generated in the working directory (the
files in the sub directory ffc_form_0_module), then I get the
following message:

OK, you don't want anything in your working directory. I didn't get
that.
Kent



_______________________________________________
DOLFIN-dev mailing list
DOLFIN-dev@xxxxxxxxxx
http://www.fenics.org/mailman/listinfo/dolfin-dev




Follow ups

References