[Ocfs2-test-devel] [PATCH 05/11] ocfs2-test: Changed configure.in to built ocfs2-test RPM.

[tristan.ye]

On Mon, 2008-11-03 at 17:53 -0500, Marcos E. Matsunaga wrote:
> hmm.. This is really interesting. 
> 
> I just re-installed openmpi on my OEL5 home machine and it does
> install on 
> /usr/lib/openmpi/1.2.5-gcc/bin/mpicc and it doesn't link to /usr/bin.

Yes marcos, I definitely got the same situation as you on OEL5 box,it
only was installed under /usr/lib/openmpi/1.2.5-gcc/bin . I manually
touch a symlink to /usr/bin or add the path to PATH to make it visible
in that case.

So we may check the MPICC as following;

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

Regards,
Tristan
	
> 
> But that's fine. I'll make the changes so that it will not check for RPM, but MPI.
> Regards,
> 
> Marcos Eduardo Matsunaga
> 
> Oracle USA
> Linux Engineering
> 
> “The statements and opinions expressed here are my own and do not
> necessarily represent those of Oracle Corporation.”
> 
> 
> Joel Becker wrote: 
> > On Fri, Oct 31, 2008 at 10:04:42AM -0400, Marcos E. Matsunaga wrote:
> >   
> > > Tristan,
> > > 
> > > I checked the openmpi-devel and they install mpicc in an unusual place
> > > (/usr/lib/openmpi/1.2.5-gcc/bin/mpicc) and which only searches the
> > > directories in the variable PATH. Since the directory where mpicc is
> > > installed is not in the PATH, which will not work.
> > >     
> > 
> > 	Um, I found it in /usr/bin on my el5 box.  It's linked to
> > /etc/alternatives/mpicc, which points back out to
> > /usr/bin/opal_wrapper-32.  But the point is that mpicc is in the PATH on
> > at least powerpc.  This is openmpi-devel-1.1.5-5.el5.
> > 
> >   
> > > Another thing is that we should only support OpenMpi in the RPM package.
> > > As for RHEL4, we can build the openmpi RPMs.
> > >     
> > 
> > 	And Tristan is right, we should be supporting MPI out of
> > packages other than the RPM.  We're not RedHat/OEL only.
> > 	For building RPMs (which are vendor-specific), you want to have
> > openmpi-devel in the BuildRequires.
> > 
> > Joel
> > 
> >