[Ocfs2-test-devel] [PATCH 05/11] ocfs2-test: Changed configure.in to built ocfs2-test RPM.
tristan.ye
tristan.ye at oracle.com
Mon Nov 3 20:08:39 PST 2008
On Mon, 2008-11-03 at 19:35 -0800, Joel Becker wrote:
> On Tue, Nov 04, 2008 at 10:43:11AM +0800, tristan.ye wrote:
> > On Mon, 2008-11-03 at 18:29 -0800, Joel Becker wrote:
> > > Where did you get your openmpi package? What's its entire name.
> > > configure.in should not be looking at rpm output. At all.
> >
> > I installed the openmpi from a tarball,
> >
> > http://www.open-mpi.org/software/ompi/v1.2/downloads/openmpi-1.2.5.tar.gz
>
> I'm thoroughly confused. If you installed it from a tarball,
> there is no rpm, so why would you query rpm?
Joel,
You mean I posted the following scripts to query the rpm?
--------------------------------------------------------------------------------------
rpm -qa|grep -q openmpi
RC=$?
if [ "${RC}" = "0" ];then #from RPM installation
MPICC=`rpm -qil openmpi-devel|grep mpicc|grep bin`
if [ ! -f ${MPICC} ];then #maybe it will show up
under /usr/bin like
Joel said
MPICC=`which mpicc`
fi
else #from SRC installation
MPICC=`which mpicc`
fi
--------------------------------------------------------------------------------------
The reason why i query the rpm here is to check the MPICC in two both
cases,so it makes the MPICC visible no matter you use rpm or tarball.
Regards,
Tristan.
>
More information about the Ocfs2-test-devel
mailing list