Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] === CREATE FAILURE ===
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-11-19 21:20:28


This patch will fix the problem -- the OMPI_VAR_SCOPE stuff didn't
make it over to the v1.2 branch:

Index: config/ompi_config_asm.m4
===================================================================
--- config/ompi_config_asm.m4 (revision 16740)
+++ config/ompi_config_asm.m4 (working copy)
@@ -801,7 +801,6 @@
      # OS X Leopard ld bus errors if you have "-g" in the link line
      # with our assembly (!). So remove it from CCASFLAGS if it's
      # there (and we're on Leopard).
- OMPI_VAR_SCOPE_PUSH([ompi_config_asm_flags_new
ompi_config_asm_flag])
      AC_MSG_CHECKING([if need to remove -g from CCASFLAGS])
      case "$host" in
          *-apple-darwin9.0*)
@@ -817,7 +816,7 @@
              AC_MSG_RESULT([no])
              ;;
      esac
- OMPI_VAR_SCOPE_POP
+ unset ompi_config_asm_flags_new ompi_config_asm_flag

      AC_MSG_CHECKING([whether to enable smp locks])
      AC_ARG_ENABLE([smp-locks],

On Nov 19, 2007, at 9:05 PM, MPI Team wrote:

>
> ERROR: Command returned a non-zero exist status
> ./configure --enable-dist
>
> Start time: Mon Nov 19 21:00:11 EST 2007
> End time: Mon Nov 19 21:05:13 EST 2007
>
> =
> ======================================================================
> [... previous lines snipped ...]
> checking size of ssize_t... 4
> checking for ptrdiff_t... (cached) yes
> checking size of ptrdiff_t... 4
> checking alignment of char... 1
> checking alignment of short... 2
> checking alignment of wchar_t... 4
> checking alignment of int... 4
> checking alignment of long... 4
> checking alignment of long long... 4
> checking alignment of float... 4
> checking alignment of double... 4
> checking alignment of long double... 4
> checking alignment of void *... 4
> checking for C bool type... no
> checking for inline... __inline__
> checking for C/C++ restrict keyword... __restrict
> checking for weak symbol support... yes
>
> *** C++ compiler and preprocessor
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for the C++ compiler vendor... gnu
> checking if C++ compiler works... yes
> configure: WARNING: -g has been added to CXXFLAGS (--enable-debug)
> checking if g++ supports -Wno-long-double... no
> configure: WARNING: -Wall -Wundef -Wno-long-long has been added to
> CXXFLAGS (--enable-picky)
> checking if g++ supports -finline-functions... yes
> configure: WARNING: -finline-functions has been added to CXXFLAGS
> checking if want C++ exception handling... no
> checking if C and C++ are link compatible... yes
> checking for C++ template_repository_directory... not used
> checking for C++ compiler template parameters... none needed
> checking if g++ supports __builtin_expect... yes
> checking if g++ supports __builtin_prefetch... yes
> checking if g++ supports const_cast<> properly... yes
> checking for C++ optimization flags... -g -Wall -Wundef -Wno-long-
> long -finline-functions
> checking for bool... yes
> checking size of bool... 1
> checking alignment of bool... 1
>
> *** Assembler
> checking dependency style of gcc... gcc3
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking for fgrep... /bin/grep -F
> ./configure: line 24662: syntax error near unexpected token
> `ompi_config_asm_flags_new'
> ./configure: line 24662: `
> OMPI_VAR_SCOPE_PUSH(ompi_config_asm_flags_new ompi_config_asm_flag)'
> =
> ======================================================================
>
> Your friendly daemon,
> Cyrador
> _______________________________________________
> testing mailing list
> testing_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/testing

-- 
Jeff Squyres
Cisco Systems