When PETSc is built with petsc4py this brings along, in some way, the 
BLAS/LAPACK that numpy is using. Yet PETSc is free to bring in its own 
BLAS/LAPACK libraries. 

  To be completely proper should we be having configure (when used with 
petsc4py) determine the BLAS/LAPACK that numpy is using and only using that for 
PETSc's BLAS/LAPACK needs?  If not, why is ok to have both sets hanging around? 
Jose's new https://gitlab.com/petsc/petsc/-/merge_requests/5737 seems to 
indicate possible problems with having both.

  Barry

Reply via email to