On Sat, Oct 16, 2010 at 22:02, Barry Smith <bsmith at mcs.anl.gov> wrote:
> Ok, config/PETSc/Configure.py will automatically put PETSC_LIB_BASIC = > -lpetsc into $PETC_ARCH/conf/petscvariables when run with single library. So you're not going to have PETSC_LIB_BASIC = -lpetscts ... -lpetscsys? This is useful because the list of library names is not constant and libpetsc changed to libpetscsys in 3.1. Lisandro (and everyone else that needs to find PETSc from configure tests) could write special code to check and use whatever is necessary, but why force that? In particular, putting them in PETSC_LIB_BASIC means that old versions of the configure scripts will still work, and new versions won't have to have a ton of branches to work with old versions of PETSc. Jed -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101016/1663569d/attachment.html>
