fenics team mailing list archive

[Balbir Thomas <balbir.thomas@xxxxxxxxx>]

All dolfin packages are installed including libdolfin0-dev. And yes dolfin.i
is in /usr/include/dolfin/swig. However package-config --cflags dolfin
results in

bt@~:$ pkg-config --cflags dolfin
-Wall -pipe -ansi -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_CHOLMOD=1
-fno-strict-aliasing -pthread
-I/home/bt/debian/sources/dolfin/dolfin-0.9.0/debian/tmp/include
-I/usr/lib/python2.5/site-packages/numpy/core/include
-I/usr/include/suitesparse -I/usr/include/python2.5
-I/usr/lib/petsc/bmake/linux-gnu-c-opt -I/usr/lib/petsc/include
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/lib -I. -I/usr/include/scotch
-I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include

Looks like this is the problem -->
-I/home/bt/debian/sources/dolfin/dolfin-0.9.0/debian/tmp/include

The include directory is being set relative to the build directory of the
debian source package. How and were does this get generated ?

I notice the following in debian/rules

        # Generate pkg-config file for DOLFIN based on pkg-config
files

        # in
scons/pkgconfig:

        python$* debian/gen_pkgconf.py debian/tmp/dolfin.pc

But am still trying to pin-point the error.

regards
bt