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
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.21-1-686
Debian Release: lenny/sid
500 unstable ftp.cz.debian.org
--- Package information. ---
Depends (Version) | Installed
=======================-+-===========
|
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
