For one - I think each external package should be packaged separately - and packagers should not rely on --download-package functionality.
Secondly - petsc/umfpack etc libs will get installed in $PREFIX/lib/python2.7/site-packages/petsc/lib only if petsc is configured with the option: --prefix=$PREFIX/lib/python2.7/site-packages/petsc/lib Perhaps there is an error here? You can check [or send us] configure.log created by PETSc. [presumably you are expecting --prefix=$PREFIX as the location to install PETSc/umfpack.] Satish On Thu, 8 Jan 2015, Juan Luis Cano wrote: > Hello all, > > I am trying to build a conda package of PETSc 3.4 using its Python build > system so anybody can install it in the Anaconda Python distribution. I need > PETSc as a dependency for FEniCS. > > The problem is that the required shared libraries (also those corresponding to > external packages such as UMFPACK) are installed in > $PREFIX/lib/python2.7/site-packages/petsc/lib. The build process goes > perfectly fine but when packaging this into a tarball these libs won't be > found by any package as they are not in $PREFIX/lib. Here is the build script > I am using: > > https://github.com/Juanlu001/conda-recipes/blob/juanlu001/fenics/petsc/build.sh > > I tried to change the destination using `--prefix` in PETSC_CONFIGURE_OPTIONS > and after `setup.py install`, but neither worked. Changing LD_LIBRARY_PATH > seems dangerous to me and creating symbolic links three levels higher seems > dirty. If the python version changes, or "lib64" is added somewhere, this will > surely break... Does anybody have a suggestion on how to do this? > > Thanks in advance, regards, > > Juan Luis >
