[mvapich-discuss] Problem Installing mvapich2-1.9

[Jonathan Perkins]

On Wed, May 08, 2013 at 10:15:59AM -0500, Bhat, Maharaj K. (GSFC-610.3)[SCIENCE SYSTEMS AND APPLICATIONS INC] wrote:
> Jonathan,
> My configure options are as shown
>  below:
> ./configure CC=pgcc CXX=pgCC F77=pgf77 FC=pgf90 CPP="pgCC -E"
> MPICHLIB_CFLAGS="-fpic -m64" MPICHLIB_CXXFLAGS="-fpic -m64"
> MPICHLIB_FFLAGS="-m64 -fpic" MPICHLIB_FCFLAGS="-m64 -fpic"
> MPICHLIB_LDFLAGS="-L/usr/lib64" --enable-f77 --enable-fc --enable-cxx
> --enable-romio --enable-threads=default --with-hwloc -disable-multi-aliases
> -enable-xrc=yes -enable-hybrid
> --prefix=/usr/local/other/SLES11.1/mvapich2/1.9/pgi-13.4.0 --disable-xml
> --disable-xml2
> 
> Looking at /etc/ ld.so.conf, we do have /lib64 before /lib, but some how the
> package links with /usr/lib/libxml2.so which is a 32 bit library.

I think this may be particular to hydra.  What happens when you add the
--with-pm=mpirun configure option.  I don't think you'll need to set
MPICHLIB_LDFLAGS in this case.

> 
> I am able to install by setting LDFLAGS="-L/usr/lib64", however with this
> setting, I see following in mpif90 script in the final install bin
> directory: 
> 
> LDFLAGS=" -L/lib -L/lib -L/usr/lib64 -L/usr/lib64 -L/lib -Wl,-rpath,/lib
> -L/lib -Wl,-rpath,/lib -L/lib -L/lib"
> 
> As you can see, the package is trying to link with 32 bit libraries in /lib.
> Because LDFLAGS settings appear in mpif90, etc., we would like to avoid
> setting this, so that we can use mpif90, etc., to compile other packages and
> use libraries in locations other than setting in mpif90.
> 
> We did not have this problem in installing earlier versions (e.g.,
> mvapich2-1.8.1), looking at mpif90 in this case, LDFLAGS is empty.

In the 1.9 series we updated to the MPICH-3.x series which featured a
large change to the build system.  It is possible that there were some
side effects with these updates.


> Any help will be greatly appreciated.
> 
> --M. K. Bhat
> 
> On 5/7/13 10:54 PM, "Jonathan Perkins" <perkinjo at cse.ohio-state.edu> wrote:
> 
> > On Tue, May 07, 2013 at 05:24:11PM -0500, Bhat, Maharaj K.
> > (GSFC-610.3)[SCIENCE SYSTEMS AND APPLICATIONS INC] wrote:
> >> I am trying to install mvapich2-1.9 . Our system OS is Linux x86_84, we have
> >> 32bit and 64 bit libraries, the 32 bit libraries are in /lib and /usr/lib,
> >> the 64 bit version libraries are in /lib64 and /usr/lib64.  We noticed there
> >> are several configure scripts that come with the mvapich2-1.9 package.  While
> >> building the package tries to use 32 bit libraries in /lib, only way I could
> >> successfully build the package is by setting LDFLAGS to "-L/usr/lib64", even
> >> with this setting, after installing, I see LDFLAGS=" -L/lib -L/lib
> >> -L/usr/lib64 -L/usr/lib64 -L/lib -Wl,-rpath,/lib -L/lib -Wl,-rpath,/lib
> >> -L/lib -L/lib" in mpif90 script in the installation bin directory.  We would
> >> like to avoid setting LDFLAGS so that it does not appear in wrapper scripts
> >> such as mpif90 which may be used to compile more packages.   Setting
> >> MPICHLIB_ related flags such as MPICHLIB_LDFLAGS does not help, the
> >> compilation (make) crashes in hydra directory when CCLD command tries to link
> >> with /usr/lib/libxml2.so ( we can see this using make -V=1).  We never had
> >> this problem with previous versions of mvapich.  Any help will be greatly
> >> appreciated.  Thanks.
> >> --M. K. Bhat
> > 
> > Have you tried using -m64 instead of setting LDFLAGS?  Also what was the
> > last version of mvapich2 that worked for you (did you try the earlier
> > 1.9 versions?)
> > 
> > If using -m64 doesn't help, you can also try disabling hydra by
> > specifying --with-pm=mpirun at configure.
> 
> 

-- 
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo