On Nov 7, 2007 9:52 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > TESTING: checkCxxCompiler from > > config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:541) > > TESTING: checkFortranCompiler from > > config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:708) > > ********************************************************************************* > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log > > for details): > > --------------------------------------------------------------------------------------- > > bin/mpif90[f77] you provided with --with-mpi-dir=/usr does not work > > Run with --with-fc=0 if you wish to use this MPI and disable Fortran > > ********************************************************************************* > > > > make: *** [build-arch] Error 1 > > dpkg-buildpackage: failure: debian/rules build gave error exit status 2 > > pbuilder: Failed autobuilding of package > > -> Aborting with an error > > -> unmounting dev/pts filesystem > > -> unmounting proc filesystem > > -> cleaning the build env > > -> removing directory /var/cache/pbuilder/build//9858 and its > > subdirectories > > > > > > Are you able to reproduce this problem? > > > I found and reported this particular problem: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450518 > > I provide a temporary fix in there, but this cannot be easily fixed in > pbuilder, until a new version of openmpi is uploaded. Fixing it by > hand and using debuild seems to make petsc build. Uff...
That problem is fixed. However, the pbuilder still fails - it should fail for you too. I discovered, that you need to change this in build-depends: gfortran | fortran-compiler to this: gfortran and when you do that, it builds in pbuilder. The problem is, that it probably calls g77, instead of gfortran. OK, so petsc seems to be ok now. I am going to try libmesh. Please don't close this issue yet - there could be other problems with g77/gfortran and maybe the proposed fix is not really a fix (i.e. causes other problems). Need to check libmesh out first. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]