On Jun 27, 2012, at 2:12 PM, Lloyd Brown wrote:
> That's a really good idea. The trouble is that I need to have multiple
> versions installed (eg. compiled with the various compilers), so I think
> I still need to manipulate name in some way, so the packages will be
> named differently. But _pre
That's a really good idea. The trouble is that I need to have multiple
versions installed (eg. compiled with the various compilers), so I think
I still need to manipulate name in some way, so the packages will be
named differently. But _prefix should definitely give me more
flexibility as to wher
Hmm. I'm not sure why --rebuild is different than not--rebuild. I'm not an
RPM expert, though...
On Jun 26, 2012, at 4:24 PM, Lloyd Brown wrote:
> Something else interesting that I just discovered. If I do this, I have
> the problem:
>
> rpmbuild --rebuild -bb path/to/openmpi-1.6-2.src.rpm
On Jun 26, 2012, at 2:40 PM, Lloyd Brown wrote:
> Is there an easy way with the .spec file and the rpmbuild command, for
> me to override the path the OpenMPI RPM installs into, in /opt?
> Basically, I'm already doing something like this:
I think all you need to do is override the RPM-builtin nam
Something else interesting that I just discovered. If I do this, I have
the problem:
rpmbuild --rebuild -bb path/to/openmpi-1.6-2.src.rpm
However, if I do an "rpm -i path/to/openmpi-1.6-2.src.rpm", and then do
very-similar rpmbuild syntax, it puts everything where I want it:
rpmbuild -bb path
Is there an easy way with the .spec file and the rpmbuild command, for
me to override the path the OpenMPI RPM installs into, in /opt?
Basically, I'm already doing something like this:
rpmbuild --rebuild --define 'install_in_opt 1' --define '_name
fsl_openmpi_intel' --define 'name fsl_openmpi_inte
