Hello Ondrej, On Fri, 2007-11-02 at 11:22 -0400, Adam C Powell IV wrote: > I've retitled this bug to your issue, which is an FTBFS, and will try to > get to it sometime next week. I'll also see if I can build and test > petsc4py and libmesh using OpenMPI. > > On Fri, 2007-11-02 at 02:48 +0100, Ondrej Certik wrote: > > Package: petsc > > > > --- Please enter the report below this line. --- > > > > Hi Adam, > > > > I have some bad news - I am not able to build the package from source. How > > to reproduce: > > > > $ sudo apt-get update > > $ apt-get source petsc > > $ cd petsc-2.3.3 > > $ debuild > > [...] > > TESTING: SGIMPICheck from > > config.packages.MPI(/home/ondra/debian/test/petsc-2.3.3/python/BuildSystem/config/packages/MPI.py:515) > > TESTING: FortranMPICheck from > > config.packages.MPI(/home/ondra/debian/test/petsc-2.3.3/python/BuildSystem/config/packages/MPI.py:525) > > ********************************************************************************* > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > > details): > > --------------------------------------------------------------------------------------- > > Fortran error! mpi_init() could not be located! > > ********************************************************************************* > > > > make: *** [build-arch] Error 1 > > debuild: fatal error at line 1237: > > debian/rules build failed
I just tried building petsc in my unstable chroot, and it worked fine. Perhaps I have a package installed which is not in the Build-Depends? Here's the post-configure Fortran build info: Fortran Compiler version: ----------------------------------------- Using C/C++ linker: Using Fortran linker: /usr/bin/mpif90 ----------------------------------------- Using libraries: -L/home/hazelsct/petsc-2.3.3/lib/linux-gnu-c-opt -L/home/hazelsct/petsc-2.3.3/lib/linux-gnu-c-opt -lpetscts -lpetscsnes -lpetscksp -lpetscdm -lpetscmat -lpetscvec -lpetsc -lX11 -L/usr/lib -L/usr/lib -lsuperlu -L/usr/lib -L/usr/lib -lumfpack -L/usr/lib -L/usr/lib -lamd -llapack-3 -lblas-3 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../.. -ldl -lmpi -lopen-rte -lopen-pal -lnsl -lutil -lgcc_s -lpthread -lmpi_f90 -lmpi_f77 -lgfortranbegin -lgfortran -lm -lm -lm -lm -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../.. -ldl -lmpi -lopen-rte -lopen-pal -lnsl -lutil -lgcc_s -lpthread -lmpi_f90 -lmpi_f77 -lgfortranbegin -lgfortran -lm -lm -lm -lm -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../.. -ldl -lmpi -lopen-rte -lopen-pal -lnsl -lutil -lgcc_s -lpthread -lmpi_f90 -lmpi_f77 -lgfortranbegin -lgfortran -lm -lm -lm -lm -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../.. -ldl -lmpi -lopen-rte -lopen-pal -lnsl -lutil -lgcc_s -lpthread -ldl Can you do me a favor and check to see whether all of those libraries are installed in your chroot? If not, then we've found the missing lib and can add that build-dep. > > But there are more serious problems: the libmesh doesn't build when petsc > > is compiled against > > openmpi and I am not able to get it run, not even the old version. Sorry I > > didn't find this earlier - I just tested my program with the binary libmesh > > package and that worked. Maybe also it was the case that it built, but > > something > > with fortran has changed, since petsc also doesn't built anymore. That's odd, I just built libmesh just fine too... > > Also petsc prints some very ugly messages, see for example: > > > > http://code.google.com/p/petsc4py/issues/detail?id=9 > > > > I fear we will have to switch to lam, to satisfy both petsc4py and libmesh. > > I am going to try to build everything myself using lam and if I succeed, > > I'll send > > you a patch. Dealt with this in the previous message. If you need lam for now to get your work done, petsc should build with it; please let me know if it doesn't. Cheers, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
