Petsc-3.3 was released half a year before hypre-2.9. The hypre developers say they noticed the bug shortly after publishing the tarball, but did not make a patch release. You can either (a) talk them into giving you/us the patch or (b) publishing a patch release with a fixed build system, or (c) fix the build system yourself and send us the patch. As soon as we have a working hypre-2.9, we'll include it in petsc-dev (and petsc-3.4, which we hope to release in a couple months).
On Wed, Jan 9, 2013 at 2:24 AM, Dominik Szczerba <dominik at itis.ethz.ch>wrote: > Hi, > > I _have_ to use hypre-2.9.0b with petsc 3.3.x (because 2.8.0b > compilation on Windows is broken due to issues with the MSVC 10 > compiler). I am aware of both 2.8.0b being officially used by petsc as > well as of Jed mentioning building problems in hypre-2.9.0b. I indeed > can not build 2.9.0b on linux due to errors but - ironically - it is > the only version I can currently build natively on Windows. Therefore > I would like to know if the decision to officially use 2.8.0b in petsc > 3.3.x is dictated exclusively by building infrastructure issues or > also by some code / API / functionality related issues. Thanks for any > comments. > > Dominik > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130109/515f1845/attachment.html>
