By build from tarball, are you saying that I can build RPMs from the
tarball, and it will work?
(keep in mind that with rocks, all software must be made into RPMs for
On Tue, Nov 2, 2010 at 10:22 AM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> Jim --
> I have an open issue about exactly this with Red Hat. I am awaiting guidance from them to know how to fix it.
> The only workaround for the moment is to build from tarball, not RPM.
> On Nov 2, 2010, at 12:47 PM, Jim Kusznir wrote:
>> Hi all:
>> I finally decided to rebuild openmpi on my cluster (last built when
>> 1.3.2 was current). I have a ROCKS cluster, so I need to build RPMs
>> to install accross the cluster rebuilds. Previously, I did so with
>> the following command:
>> rpmbuild -bb --define 'install_in_opt 1' --define 'install_modulefile
>> 1' --define 'modules_rpm_name environment-modules' --define
>> 'build_all_in_one_rpm 0' --define 'configure_options
>> --with-tm=/opt/torque' --define '_name openmpi-gcc' --define 'makeopts
>> -J8' openmpi-1.3.2.spec
>> With 1.5, this fails with:
>> configure: WARNING: *** This configure script does not support
>> --program-prefix, --program-suffix or --program-transform-name. Users
>> are recommended to instead use --prefix with a unique directory and
>> make symbolic links as desired for renaming.
>> configure: error: *** Cannot continue
>> I thought it might have been the --define '_name ...', so I removed
>> that, but got the same error.
>> For me, the _name is important, as I build for two different compilers
>> and need to have the resulting RPMs named accordingly (and have them
>> installed in their own /opt/opemmpi-gcc, etc directories).
>> Any suggestions how to proceed? (the specific version of openmpi in
>> this case is the one available for download on Nov 2 from the main
>> website; obtained via the src.rpm download)
>> users mailing list
> Jeff Squyres
> For corporate legal information go to:
> users mailing list