On Thu, Dec 22, 2011 at 9:11 AM, Chekuri S. Choudary < cchoudary at rnet-tech.com> wrote:
> ** ** > > I am building an RPM for petsc-3.2-p5. I would like the users of the RPM > to be able to mention the PETSC_DIR at installation time, i.e, the RPM > should be relocatable.**** > > For example, **** > > rpm ?ivh --prefix=$HOME/petsc**** > > export PETSC_DIR=$HOME/petsc **** > > ** ** > > The issue is that while building the RPM, the ?configure ?prefix=$DIR? > builds the package assuming that $DIR is the final location of the files. > So, the only way seems to be to decide the**** > > installation path upfront and make the RPM non relocatable.**** > > ** ** > > Even with PETSC_DIR and PETSC_ARCH, it looks like the path is being > hardcoded, i.e, once PETSc is built, the files cannot be simply moved by > changing PETSC_DIR and PETSC_ARCH. I was wondering if there is workaround > for this issue or if I am missing anything. > No, we do not support relocatable binary packages. There are too many things to do during the build. Matt > > > ** > > Thanks**** > > Shiva**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20111222/d823000e/attachment.html>