dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Mon, Jul 04, 2005 at 08:26:17PM -0400, Faheem Mitha wrote:

> On Mon, 4 Jul 2005, Anders Logg wrote:
> 
> >I guess you have seen that we have now updated to PETSc 2.3.0...
> 
> Yes, I saw the message. However, I will wait till you have released a
> stable version of DOLFIN which uses PETSc 2.3 before thinking about
> this.
> 
> Do you have an estimate for when this will happen?

I'm ready to release. I'm just waiting for Rob Kirby to release a
new version of FIAT, so we can release new versions of FIAT + FFC +
DOLFIN at the same time.

My guess is tomorrow.

> For the moment, I am just trying to get the current DOLFIN version
> 0.5.7 packaged ASAP so we can try and use it.
> 
> >Can you send the output from DOLFINs configure? In particular the part
> >where it says "using PETSC_DIR...".
> 
> See below.
> 
> >Maybe this will be useful if we decide to provide precompiled packages
> >for DOLFIN, but the best thing would be if PETSc (and DOLFIN) was
> >available directly from Debian.
> 
> Agreed. The only reason I am doing packaging is that the PETSc Debian 
> package is out of date, and I don't know when it will be updated. We need 
> it *now*, and can't wait. Once official packages are available, that will 
> be the end of packaging efforts on my part.
> 
> I think it will be easy to update PETSc and DOLFIN once I have packaged 
> one version.

I think so too. After the summer, we might set up some automatic
packaging scripts to create and distribute Debian packages of PETSc +
all FEniCS projects. Then your scripts might be very useful. Tell me
if you happen to create packages of FFC and FIAT.

> I am happy to send you whatever debugging information you require, but
> don't you think it would more efficient if you were to install my
> package in a chroot or something, and try to compile DOLFIN against
> it? 

Yes, for you but not for me... ;-)

>From the configure output below, it looks like PETSC_DIR is set
correctly. Can you try to do the following in a shell:

    make -s -C $PETSC_DIR getincludedirs PETSC_DIR=$PETSC_DIR

Make sure you have defined PETSC_DIR first. Does this produce some
reasonable output? You should get something like

-I/usr/local/lib/petsc -I/usr/local/lib/petsc/bmake/linux-gnu -I/usr/local/lib/petsc/include

> I think you said you use Debian...

Yes.

> Just one more question. When DOLFIN was using PETSc 2.2.0, did it compile 
> correctly against Powell's 2.2.0 Debian package?

Yes.

/Anders

>                                                               Faheem.
> 
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets $(MAKE)... yes
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for ranlib... ranlib
> checking for gawk... gawk
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking for an ANSI C-conforming const... yes
> checking for inline... inline
> checking how to run the C preprocessor... gcc -E
> checking for egrep... 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 for size_t... yes
> turning on debugging and warnings (use --enable-optimization to avoid 
> this).
> enabling debugging compiler flags
> enabling curses, use --disable-curses to disable
> checking for library containing wbkgdset... -lncurses
> using PETSC_DIR=/usr/lib/petsc-2.2.1
> assuming PETSc BOPT is g_c++
> checking for configarch... yes
> make: *** No rule to make target `getincludedirs'.  Stop.
> make: *** No rule to make target `getlinklibs'.  Stop.
> checking for mpirun... yes
> checking for xml2-config... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating src/Makefile
> config.status: creating src/pre/Makefile
> config.status: creating src/kernel/Makefile
> config.status: creating src/kernel/common/Makefile
> config.status: creating src/kernel/common/dolfin/Makefile
> config.status: creating src/kernel/fem/Makefile
> config.status: creating src/kernel/fem/dolfin/Makefile
> config.status: creating src/kernel/function/Makefile
> config.status: creating src/kernel/function/dolfin/Makefile
> config.status: creating src/kernel/form/Makefile
> config.status: creating src/kernel/form/dolfin/Makefile
> config.status: creating src/kernel/io/Makefile
> config.status: creating src/kernel/io/dolfin/Makefile
> config.status: creating src/kernel/la/Makefile
> config.status: creating src/kernel/la/dolfin/Makefile
> config.status: creating src/kernel/main/Makefile
> config.status: creating src/kernel/main/dolfin/Makefile
> config.status: creating src/kernel/math/Makefile
> config.status: creating src/kernel/math/dolfin/Makefile
> config.status: creating src/kernel/mesh/Makefile
> config.status: creating src/kernel/mesh/dolfin/Makefile
> config.status: creating src/kernel/ode/Makefile
> config.status: creating src/kernel/ode/dolfin/Makefile
> config.status: creating src/kernel/quadrature/Makefile
> config.status: creating src/kernel/quadrature/dolfin/Makefile
> config.status: creating src/kernel/log/Makefile
> config.status: creating src/kernel/log/dolfin/Makefile
> config.status: creating src/kernel/settings/Makefile
> config.status: creating src/kernel/settings/dolfin/Makefile
> config.status: creating src/modules/Makefile
> config.status: creating src/modules/dolfin/Makefile
> config.status: creating src/modules/poisson/Makefile
> config.status: creating src/modules/poisson/dolfin/Makefile
> config.status: creating src/modules/convdiff/Makefile
> config.status: creating src/modules/convdiff/dolfin/Makefile
> config.status: creating src/modules/elasticity/Makefile
> config.status: creating src/modules/elasticity/dolfin/Makefile
> config.status: creating src/modules/elasticity-updated/Makefile
> config.status: creating src/modules/elasticity-updated/dolfin/Makefile
> config.status: creating src/modules/navierstokes/Makefile
> config.status: creating src/modules/navierstokes/dolfin/Makefile
> config.status: creating src/config/Makefile
> config.status: creating src/post/Makefile
> config.status: creating src/demo/Makefile
> config.status: creating src/demo/bench/Makefile
> config.status: creating src/demo/la/Makefile
> config.status: creating src/demo/solvers/Makefile
> config.status: creating src/demo/solvers/navierstokes/Makefile
> config.status: creating src/demo/solvers/ode/Makefile
> config.status: creating src/demo/solvers/ode/modeling/Makefile
> config.status: creating src/demo/solvers/ode/homotopy/Makefile
> config.status: creating src/utils/Makefile
> config.status: creating src/utils/inp2dx/Makefile
> config.status: creating src/greeting/Makefile
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev
> 

-- 
Anders Logg
Research Assistant Professor
Toyota Technological Institute at Chicago
http://www.tti-c.org/logg/