you might want to have a look here if you need a working example of
We used to generate both SRPMs and RPMs for Open MPI in a previous
project and did in fact specify a separate installation directory :
(%define ompi_prefix /opt/i2g/openmpi in i2g-openmpi.spec.in)
Hope that helps.
On Fri, 2009-10-02 at 03:48 -0700, Bill Johnstone wrote:
> I'm trying to build an RPM of 1.3.3 from the SRPM. Despite typical RPM practice, I need to build ompi so that it installs to a different directory from /usr or /opt, i.e. what I would get if I just built from source myself with a --prefix argument to configure.
> When I invoke buildrpm with the --define 'configure_options --prefix=<desired path> ...', the options do get set when the building process gets kicked off. However, when I query the final RPM, only vampirtrace has paid attention to the specified --prefix and wants to place its files accordingly. How should I alter the .spec file (or in some other place?) to get the desired behavior for the final file locations in the RPM?
> Thank you for any help.
> users mailing list
Dipl.-Inf. Kiril Dichev
Tel.: +49 711 685 60492
High Performance Computing Center Stuttgart (HLRS)