> When I tried to compile libmesh0.6.4 against libpetsc 3.1 I > discovered that libpetsc had gone through an API change. libmesh > tried to call a petsc function with the wrong number of arguments. > So I guess there has been an API change in libpetsc. Perhaps the API > change was at libpetsc 3.0 and libmesh0.6.4 didn't compile with that > either? I reported it here: https://sourceforge.net/tracker/?func=detail&aid=3084266&group_id=71130&atid=530254
Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
