On Tue, Mar 22, 2011 at 11:09 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> > We need to make the specific tar file version more transparent: > > When the tarball is generated should a nice list of the tarballs for each > external packages be automatically generated and put somehow in the > document? Should we have a tool that extracts that information from the > appropriate XXX.py upon request? How to tell people about this tool? If we > have to tell them about the tool we might as just well tell them to look in > the appropriate config/PETSc/packages/XXXX.py or > config/BuildSystem/config/packagesXXX.py directly? > How about ./configure --packgeInfo hypre ==> Hypre 2.6.0b http://ftp.mcs.anl.gov/pub/petsc/externalpackages/hypre-2.6.0b.tar.gz Matt > Barry > > > > On Mar 22, 2011, at 11:02 AM, Satish Balay wrote: > > > Which version of PETSc are you using? The URL for hypre is listed in > > config/PETSc/packages/hypre.py - for any given version of petsc. > > > > for petsc-3.1 its: > http://ftp.mcs.anl.gov/pub/petsc/externalpackages/hypre-2.6.0b.tar.gz > > > > Satish > > > > On Tue, 22 Mar 2011, Verena Kuhlemann wrote: > > > >> Hello, > >> > >> I was wondering which version of HYPRE one should use with Petsc. I need > to > >> download it before > >> the configuration of Petsc as --download-hypre=1 is not working for me. > >> > >> Thanks, > >> Verena > >> > > > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20110322/0e6fd2d9/attachment.htm>
