Open MPI logo

Open MPI User's Mailing List Archives

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

From: Michael Kluskens (mkluskens_at_[hidden])
Date: 2006-03-23 17:32:17


I have Absoft version 8.2a installed on my OS X 10.4.5 system and in
order to do some testing I was trying to build OpenMPI 1.1a1r9364
with it and got the following funny result:

*** Fortran 77 compiler
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f95 accepts -g... yes
checking if Fortran 77 compiler works... yes
checking f95 external symbol convention... upper case
checking if Fortran 77 compiler supports LOGICAL... yes
checking size of Fortran 77 LOGICAL...
checking for C type corresponding to LOGICAL... not found
configure: WARNING: *** Did not find corresponding C type
configure: error: Cannot continue

Note that f95 is/should be my Absoft compiler but the configure
script flags it as the GNU Fortran 77 compiler.

I had set FC and F77 to f95.

The config.log is attached and the terminal display is pasted below:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes

========================================================================
====
== Configuring Open MPI
========================================================================
====

*** Checking versions
checking Open MPI version... 1.1a1r9364
checking Open MPI Subversion repository version... r9364
checking Open Run-Time Environment version... 1.1a1r9364
checking Open Run-Time Environment Subversion repository version...
r9364
checking Open Portable Access Layer version... 1.1a1r9364
checking Open Portable Access Layer Subversion repository version...
r9364

*** Initialization, setup
configure: builddir: /Users/mkluskens/Public/MPI/OpenMPI/
openmpi-1.1a1r9364
configure: srcdir: /Users/mkluskens/Public/MPI/OpenMPI/
openmpi-1.1a1r9364
checking build system type... powerpc-apple-darwin8.5.0
checking host system type... powerpc-apple-darwin8.5.0
checking for prefix by checking for ompi_clean... no
installing to directory "/usr/local"

*** Configuration options
checking Whether to run code coverage... no
checking whether to debug memory usage... no
checking whether to profile memory usage... no
checking if want developer-level compiler pickyness... no
checking if want developer-level debugging code... no
checking if want Fortran 77 bindings... yes
checking if want Fortran 90 bindings... yes
checking whether to enable PMPI... yes
checking if want C++ bindings... yes
checking if want to enable weak symbol support... yes
checking if want run-time MPI parameter checking... runtime
checking if want to install OMPI header files... no
checking if want pretty-print stacktrace... yes
checking if want deprecated executable names... no
checking max supported array dimension in F90 MPI bindings... 4
checking if pty support should be enabled... yes
checking if user wants dlopen support... yes
checking if heterogeneous support should be enabled... yes
checking if want trace file debugging... no

========================================================================
====
== Compiler and preprocessor tests
========================================================================
====

*** C compiler and preprocessor
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for the C compiler vendor... gnu
checking if gcc supports -finline-functions... yes
checking if gcc supports -fno-strict-aliasing... yes
configure: WARNING: -fno-strict-aliasing has been added to CFLAGS
checking for C optimization flags... -O3 -DNDEBUG -fno-strict-aliasing
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for long long... yes
checking for long double... yes
checking for int8_t... yes
checking for uint8_t... yes
checking for int16_t... yes
checking for uint16_t... yes
checking for int32_t... yes
checking for uint32_t... yes
checking for int64_t... yes
checking for uint64_t... yes
checking for intptr_t... yes
checking for uintptr_t... yes
checking for mode_t... yes
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 4
checking for long long... (cached) yes
checking size of long long... 8
checking for long double... (cached) yes
checking size of long double... 16
checking for float... yes
checking size of float... 4
checking for double... yes
checking size of double... 8
checking for void *... yes
checking size of void *... 4
checking for size_t... yes
checking size of size_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... 16
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... no

*** 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 if C++ compiler works... yes
checking for the C++ compiler vendor... gnu
checking if g++ supports -finline-functions... yes
configure: WARNING: -finline-functions has been added to CXXFLAGS
checking if want C++ exception handling... no
checking for C++ template_repository_directory... not used
checking for C++ compiler template parameters... none needed
checking for C++ optimization flags... -O3 -DNDEBUG -finline-functions
checking for bool... yes
checking size of bool... 4
checking alignment of bool... 4

*** Assembler
checking for BSD-compatible nm... /usr/bin/nm -p
checking for fgrep... grep -F
checking whether to enable smp locks... yes
checking directive for setting text section... .text
checking directive for exporting symbols... .globl
checking for objdump... no
checking if .note.GNU-stack is needed... no
checking suffix for labels... :
checking prefix for global symbol labels... _
checking prefix for lsym labels... L
checking prefix for function in .type...
checking if .size is needed... no
checking if .align directive takes logarithmic value... yes
checking if PowerPC registers have r prefix... yes
checking for 64-bit PowerPC assembly support... no
checking if gcc supports GCC inline assembly... yes
checking if gcc supports DEC inline assembly... no
checking if gcc supports XLC inline assembly... no
checking if g++ supports GCC inline assembly... yes
checking if g++ supports DEC inline assembly... no
checking if g++ supports XLC inline assembly... no
checking for assembly format... default-.text-.globl-:-_-L--0-1-1-0-0
checking for asssembly architecture... POWERPC32
checking for perl... perl
checking for pre-built assembly file... yes (atomic-powerpc32-osx.s)
checking for atomic assembly filename... atomic-powerpc32-osx.s

*** Fortran 77 compiler
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f95 accepts -g... yes
checking if Fortran 77 compiler works... yes
checking f95 external symbol convention... upper case
checking if Fortran 77 compiler supports LOGICAL... yes
checking size of Fortran 77 LOGICAL...
checking for C type corresponding to LOGICAL... not found
configure: WARNING: *** Did not find corresponding C type
configure: error: Cannot continue