Home
last modified time | relevance | path

Searched hist:d093bd8d97bae0b8a8d5cea6701393b27d24d008 (Results 1 – 4 of 4) sorted by relevance

/petsc/config/BuildSystem/config/packages/
H A Df2cblaslapack.pyd093bd8d97bae0b8a8d5cea6701393b27d24d008 Fri Aug 22 03:52:46 UTC 2014 Barry Smith <bsmith@mcs.anl.gov> For --prefix configurations the external packages are installed directly to the final location
Previously we installed to the PETSC_DIR/PETSC_ARCH location and then copied everything over at the time of the PETSc make install
The reason was so only a single sudo would ever be needed. The drawback was it does not leverage each packages install tools, so, for example,
--download-mpich didn't work correctly with --prefix and also shared libraries did not work correctly with --prefix

If the final location requires root access then that is now requested via sudo for each external packages make install, but if sudo is not needed
it is not called
H A DMPI.pyd093bd8d97bae0b8a8d5cea6701393b27d24d008 Fri Aug 22 03:52:46 UTC 2014 Barry Smith <bsmith@mcs.anl.gov> For --prefix configurations the external packages are installed directly to the final location
Previously we installed to the PETSC_DIR/PETSC_ARCH location and then copied everything over at the time of the PETSc make install
The reason was so only a single sudo would ever be needed. The drawback was it does not leverage each packages install tools, so, for example,
--download-mpich didn't work correctly with --prefix and also shared libraries did not work correctly with --prefix

If the final location requires root access then that is now requested via sudo for each external packages make install, but if sudo is not needed
it is not called
/petsc/config/BuildSystem/config/
H A Dpackage.pyd093bd8d97bae0b8a8d5cea6701393b27d24d008 Fri Aug 22 03:52:46 UTC 2014 Barry Smith <bsmith@mcs.anl.gov> For --prefix configurations the external packages are installed directly to the final location
Previously we installed to the PETSC_DIR/PETSC_ARCH location and then copied everything over at the time of the PETSc make install
The reason was so only a single sudo would ever be needed. The drawback was it does not leverage each packages install tools, so, for example,
--download-mpich didn't work correctly with --prefix and also shared libraries did not work correctly with --prefix

If the final location requires root access then that is now requested via sudo for each external packages make install, but if sudo is not needed
it is not called
/petsc/config/PETSc/
H A DConfigure.pyd093bd8d97bae0b8a8d5cea6701393b27d24d008 Fri Aug 22 03:52:46 UTC 2014 Barry Smith <bsmith@mcs.anl.gov> For --prefix configurations the external packages are installed directly to the final location
Previously we installed to the PETSC_DIR/PETSC_ARCH location and then copied everything over at the time of the PETSc make install
The reason was so only a single sudo would ever be needed. The drawback was it does not leverage each packages install tools, so, for example,
--download-mpich didn't work correctly with --prefix and also shared libraries did not work correctly with --prefix

If the final location requires root access then that is now requested via sudo for each external packages make install, but if sudo is not needed
it is not called