[mpich-discuss] Problems with configuring MPICH with cross compiler

[chan at mcs.anl.gov]

----- "junli gu" <gujunli at gmail.com> wrote:

> Yes. The configuration finished successfully with --disable-romio.
> Interesting. But I am not sure whether the binaries it produced are
> correct alpha binaries.

Try do a file command on the binary created by mpicc, e.g. file a.out.
(mpicc should use alpha-gcc as compiler/linker)

> And I am confused with another question. What does the binaries have
> produced by mpicc? Do they have the runtime information for
> running?And What
> does the mpiexec do? Does it need the runtime lib ?I want to run the
> binaries on a simulator, I used the comman as usual:
> mpiexec -np 4 /benchmark/hello
> The simulator said no mpiexec command. That's not wired. I am trying
> to install MPICH on disk image of the simulator. If it does not work, Is
> there any option that I can run the binaries without mpiexec command？

You need to install MPICH2 to a filesystem accessible by your simulator.
The --prefix option specifies the install directory, and "make install"
will install all the relevant files to the install directory.  The README
file or the install guide has more details. 

The default process manager is mpd which requires python.  I am not sure
your simulator has python.  But since it is a simulator, you could use
gforker (or maybe hydra)

mpiexec.gforker -n 4 cpilog

(or mpiexec.hydra -n 4 cpilog)

A.Chan

> 
> Thank you very much. I will report for further problems.
> 2009/11/11 <chan at mcs.anl.gov>
> 
> >
> > It looks like the test for MPI_Offset at the end of top-level
> configre.in
> > broke the cross-compile support in MPICH2.  Can you file a bug
> report at
> > mpich2-maint at mcs.anl.gov and send in your config.log and tee.txt
> > as well as your configure command that failed ?
> >
> > There is a distclean target in Makefile but since configure
> > failed so no Makefile was created, i.e. no need to do "make
> distclean".
> > (I should have seen this earlier)
> >
> > If your don't need MPI-IO, i.e. romio, you can try the following to
> > see if the configure completes:
> >
> > ./configure --prefix=/home/junligu/shared/MPICH_alpha2
> > --enable-cxx --disable-f77 --disable-romio
> > --with-device=ch3:nemesis --with-atomic-primitives=no
> > --build=i386-unknown-linux-gnu --host=alpha-unknown-linux-gnu
> >
> > Let us know how it goes.
> >
> > A.Chan
> >
> > ----- "junli gu" <gujunli at gmail.com> wrote:
> >
> > > Thank you very much for help!
> > >
> > > I did as you said. But the problem keeps the same. I have
> attached
> > > the
> > > output of configuring process in tee.txt . the the other
> information
> > > is in
> > > config.log.
> > >
> > > By the way waht do you mean by "make dist clean"? I tried but
> there is
> > > make:
> > > *** No rule to make target `distclean'.  Stop.
> > > "".
> > >
> > > I hope you can look to it further. Thank you !
> > > 2009/11/11 <chan at mcs.anl.gov>
> > >
> > > >
> > > > ----- "junli gu" <gujunli at gmail.com> wrote:
> > > >
> > > >
> > > > >   "export
> > > > >
> > > >
> > >
> >
> DRIVER_PATH=/opt/crosstool/gcc-3.4.3-glibc-2.3.5/alpha-unknown-linux-gnu/alpha-unknown-linux-gnu/
> > > > >   export GCC=${DRIVER_PATH}/bin/alpha-gcc
> > > > >   export CC=${DRIVER_PATH}/bin/alpha-gcc
> > > > >   export CXX=${DRIVER_PATH}/bin/g++
> > > > >   export AR=${DRIVER_PATH}/bin/ar
> > > > >   export LD=${DRIVER_PATH}/bin/ld
> > > > >   ./configure --prefix=/home/junligu/shared/MPICH_alpha2
> > > --enable-cxx
> > > > > --disable-f77 --with-device=ch3:nemesis
> > > --with-atomic-primitives=no
> > > > > --target=alpha-unknown-linux-gnu --host=i386-unknown-linux-gnu
>  "
> > > > >
> > > >
> > > > It seems you might have specified --host incorrectly, replace
> > > > your --host and --target options by the followings:
> > > >
> > > > --build=i386-unknown-linux-gnu --host=alpha-unknown-linux-gnu
> > > >
> > > > (see
> > > >
> > > >
> > >
> >
> http://www.gnu.org/software/autoconf/manual/autoconf.html#Specifying-Target-Triplets
> > > > )
> > > >
> > > > Be sure to do a "make distclean" before reconfiguring mpich2.
> > > > If the problem persists, send us the configure and make outputs
> > > > as seen on your terminal (It is possible that cross-compile
> support
> > > > is still buggy)
> > > >
> > > > BTW, your stderr message should be piped to the configure
> output
> > > > file as it will help us to identify any potential problem/bug
> > > faster.
> > > > If you are not familiar with piping stderr and stdout to 1
> file,
> > > > see the mpich2's README or installer's guide.
> > > >
> > > > A.Chan
> > > > _______________________________________________
> > > > mpich-discuss mailing list
> > > > mpich-discuss at mcs.anl.gov
> > > > https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
> > > >
> > >
> > >
> > >
> > > --
> > > ************************************************
> > > Gu Junli--谷俊丽
> > > PHD Candidate of Tsinghua University
> > > Beijing 100084,China
> > > Tel: 86-10-62795139
> > >
> > > ************************************************
> >
> 
> 
> 
> -- 
> ************************************************
> Gu Junli--谷俊丽
> PHD Candidate of Tsinghua University
> Beijing 100084,China
> Tel: 86-10-62795139
> 
> ************************************************