retitle 448158 FTBFS: Fortran MPI check fails thanks Hello Ondrej,
This is a separate issue, and should have been a new bug. The limited platform availability of OpenMPI is a non-issue, and I was about to close it after a week of inactivity. 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. LAM development has stopped, and its developers have moved to OpenMPI. Please see item 9 in http://www.open-mpi.org/faq/?category=general and the LAM homepage at http://www.lam-mpi.org/ for more info. I therefore feel very strongly that it is worth trying to make OpenMPI the primary base for MPI software in the lenny release, rather than reverting to the deprecated lam distribution. On the other hand, the lam build option for PETSc should still work using "fakeroot debian/rules PETSC_MPI=lam binary" -- or if it doesn't work, then please file a separate bug against petsc. Next time please check the bug more carefully to see if it is the same thing you're reporting, and if it's not, then open a new one. Thanks, Adam 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 > > > 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. > > 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. > > Ondrej -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
