On Mar 22, 2011, at 11:22 AM, Satish Balay wrote: > If --download-package doesn't work - it prints the URL of the package. > > If we need to document this further - 'configure --help' should print > the defulat URLs for packages.
Yes it should print it! The problem is that --help also prints a ton of stuff that gets confusing and in the way of important things. Better way to organize the output? Barry > Satish > > On Tue, 22 Mar 2011, Barry Smith 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? >> >> 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 >>>> >>> >> >> >
