Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] OpenMPI 1.2.5 configure bug for POWERPC64 target
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-02-27 10:34:37

On Feb 23, 2008, at 10:05 AM, Mathias PUETZ wrote:

> 1. Could you please fix the bug above in the configure script ?

Thanks for the detailed ananlysis. Can you confirm that this patch
works for you before I commit it:

Index: config/ompi_config_asm.m4
--- config/ompi_config_asm.m4 (revision 17620)
+++ config/ompi_config_asm.m4 (working copy)
@@ -1047,7 +1047,7 @@
              AC_MSG_CHECKING([whether possible to generate assembly
              mkdir -p opal/asm/generated
- ompi_try='$PERL $top_ompi_srcdir/opal/asm/
$ompi_cv_asm_arch $ompi_cv_asm_format $top_ompi_srcdir/opal/asm/base
$top_ompi_builddir/opal/asm/generated/$ompi_cv_asm_file >conftest.out
+ ompi_try='$PERL $top_ompi_srcdir/opal/asm/
$ompi_cv_asm_arch "$ompi_cv_asm_format" $top_ompi_srcdir/opal/asm/base
$top_ompi_builddir/opal/asm/generated/$ompi_cv_asm_file >conftest.out
              if AC_TRY_EVAL(ompi_try) ; then
                  # save the warnings
                  cat conftest.out >&AC_FD_CC

> 2. Could someone explain, why configure might determine a different
> ompi_cv_asm_format
> than stated in the asm-data.txt database ?
> Maybe the meaning of the cryptic assmebler format string is
> explained somewhere.
> If so, could someone point me to the explanation ?

I have to defer to Brian on this one...

Jeff Squyres
Cisco Systems