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

[tristan.ye]

On Mon, 2008-11-03 at 18:35 -0800, Joel Becker wrote:
> On Tue, Nov 04, 2008 at 09:58:28AM +0800, tristan.ye wrote:
> > On Mon, 2008-11-03 at 15:33 -0800, Joel Becker wrote:
> > > On Mon, Nov 03, 2008 at 05:53:37PM -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.
> > > 
> > > 	What does /usr/bin/mpicc have?  LAM?  Anything?  Is there an
> > > /etc/alternatives/mpicc?
> > 
> > Joel,
> > 
> > The mpicc you've seen under /usr/bin should be a part of lammpi, which
> > lead to a confusion since lammpi and openmpi use the same name of their
> > generic binaries(such as mpirun,mpicc,mpiexec), it maybe the reason why
> > openmpi RPM package installed their binaries into such a strange
> > directory(try to avoid affecting the existing mpi product?),and I'm sure
> > a /etc/alternatives/mpicc also do not belong to the openmpi package,you
> > can check with rpm -ql openmpi-devel
> > 
> > Any way,it will be great helpful to do a cleanup for any other mpi
> > products before you jump to openmpi.
> 
> 	I don't have any other mpi products installed.  Certainly not
> lammpi.  /etc/alternatives is not owned by any package precisely because
> it is managed in %post scripts.  To wit:
> 
> --------------------------------------------------------------------
> [root at ca-test39 ~]# rpm -q --scripts openmpi-devel
> postinstall scriptlet (using /bin/sh):
> alternatives --install  /usr/bin/mpicc mpicc \
> 			/usr/bin/opal_wrapper-32 11 \
> 	--slave /usr/bin/mpic++ mpic++ /usr/bin/opal_wrapper-32 \
> 	--slave /usr/bin/mpiCC mpiCC /usr/bin/opal_wrapper-32 \
> 	--slave /usr/bin/mpicxx mpicxx /usr/bin/opal_wrapper-32 \
> 	--slave /usr/bin/mpif77 mpif77 /usr/bin/opal_wrapper-32 \
> 	--slave /usr/bin/mpif90 mpif90 /usr/bin/opal_wrapper-32
> preuninstall scriptlet (using /bin/sh):
> if [ "$1" -eq 0 ]; then
>     alternatives --remove mpicc /usr/bin/opal_wrapper-32
> fi
> postuninstall program: /sbin/ldconfig
> --------------------------------------------------------------------
> 
> 	That's openmpi-devel using the 'alternatives' program to update
> the /usr/bin/mpicc symlink.  It manages these symlinks via
> /etc/alternatives.  For more info:
> 
> --------------------------------------------------------------------
> [root at ca-test39 ~]# rpm -q openmpi-devel
> openmpi-devel-1.1.1-5.el5
Since i installed the openmpi via a tarball currently,so have not such
devel rpm installed.

I also have installed the openmpi via rpm by ULN channel. i remember its
version is 1.2.5-5, will you try that version to see if things will be
different?


> [root at ca-test39 ~]# rpm -qf $(which alternatives)
> chkconfig-1.3.30.1-1
[root at ocfs2-test6 data]# rpm -qf $(which alternatives)
chkconfig-1.3.30.1-1

> [root at ca-test39 ~]# cat /etc/redhat-release 
> Red Hat Enterprise Linux Server release 5 (Tikanga)
> --------------------------------------------------------------------
[root at ocfs2-test6 data]# cat /etc/redhat-release 
Enterprise Linux Enterprise Linux Server release 5.1 (Carthage)

> 
> 	So, can you tell me what version of openmpi-devel you have?
> What version of OEL?  Basically the same info as above.
> 
> Joel
>