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

[Dave Goodell]

Unfortunately, alpha is not a supported platform for nemesis (or most  
of the other channels).  We might add support some day, although at  
this point it is difficult to actually find an alpha machine on which  
we can do the development work.

Your best bet is probably to configure with "--with-device=ch3:sock",  
which shouldn't require any atomic operations or have any special  
memory usage requirements.  Performance won't be as good as  
ch3:nemesis if it did work, but there's no way that nemesis will work  
on alpha in the near future.

-Dave

On Nov 11, 2009, at 4:41 PM, junli gu wrote:

> I realize that I set the option --with-atomic-primitives=no to get  
> through the configuration. " OpenPA can emulate atomic primitives  
> using
> locks by specifying --with-atomic-primitives=no but performance will  
> be very poor.  This override should only be specified for correctness
> testing purposes."  I am afraid that I won't accept the performance  
> to be very poor.
>
> If I don't set this option, the configuration fails again.
> I attached the stderr message file screen nemesis.txt, the screen  
> output file nemesis.txt and the config.log. Please check.
>
> If I set the --with-device=ch3:shm, there is also error from  
> checking for x86 mfence instruction using __asm__. I can provide the  
> files including the output information like the above if needed.
>
> 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
>
> ************************************************
> < 
> nemesis 
> .txt 
> > 
> < 
> screen_nemesis 
> .txt><config.log>_______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss