Since MPE uses autoconf's AC_C_BIGENDIAN to define byte ordering, using
anything other than WORDS_BIGENDIAN will mean MPE cannot uses
AC_C_BIGENDIAN. It also means any package that needs to know byte
ordering cannot uses AC_C_BIGENDIAN with LAM. Does LAM define byte
ordering through AC_C_BIGENDIAN as well ? Or it has some other mechanism
to define WORDS_BIGENDIAN ? (In older LAM, LAM and MPE were able to play
nicely together on intel box. The offending statements in lam_config.h
seems to be added recently ? )
A.Chan
On Tue, 10 Sep 2002, Mark Hartner wrote:
> MPICH 1.2.4 and LAM 6.5.6 both use WORDS_BIGENDIAN
>
>
> lam_config.h does:
>
> #ifndef WORDS_BIGENDIAN
> #define WORDS_BIGENDIAN 0
> #endif
>
> and the MPE source does:
>
> #ifndef WORDS_BIGENDIAN
>
> See the problem here? For a little endian machine the LAM source #def's
> WORDS_BIGENDIAN, and then MPICH sees that it is defined and compiles for a
> big endian machine.
>
> We are using a "little endian" intel box and noticed that the MPE traces
> were complete garbage. Replacing WORDS_BIGENDIAN with MPE_WORDS_BIGENDIAN
> in the MPICH source fixed the problem and now LAM/MPE are working fine.
>
> Mark
>
>
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
