Hi,

> Can you send the config.log for the platform where it failed?
> 
> I'd like to see the specific compiler error that occurred.

I found the error with your hint. For Open MPI 1.6.x I must also
specify "F77" and "FFLAGS" for the Fortran 77 compiler. Otherwise
it uses "gfortran" from the GNU package. "gfortran" worked for the
64 bit version and didn't work for the 32 bit version. (that's the
reason why I got only an error for the 32 bit version).


Open MPI 1.6.4:
---------------
...
  $ ../openmpi-1.6.4a1r27643/configure --prefix=/usr/local/openmpi-1.6.4_32_cc 
LDFLAGS=-m32 CC=cc CXX=CC FC=f95 CFLAGS=-m32 CXXFLAGS=-m32 -library=stlport4 
FCFLAGS=-m32 CPP=cpp CXXCPP=cpp CPPFLAGS= CXXCPPFLAGS= C_INCL_PATH= 
C_INCLUDE_PATH= CPLUS_INCLUDE_PATH= OBJC_INCLUDE_PATH= OPENMPI_HOME= 
--enable-cxx-exceptions --enable-heterogeneous --enable-opal-multi-threads 
--enable-mpi-thread-multiple --with-threads=posix --with-hwloc=internal 
--without-openib --without-udapl --with-wrapper-cflags=-m32 --enable-debug
...
ac_cv_env_CXX_value=CC
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FCFLAGS_set=set
ac_cv_env_FCFLAGS_value=-m32
ac_cv_env_FC_set=set
ac_cv_env_FC_value=f95
...
configure:36508: checking if Fortran 77 compiler supports INTEGER*16
configure:36524: gfortran -c  conftest.f >&5
configure:36524: $? = 0
configure:36537: result: yes
configure:36572: checking size of Fortran 77 INTEGER*16
configure:36640: cc -m32 -g  -I. -c conftest.c
configure:36647: $? = 0
configure:36657: gfortran  conftestf.f conftest.o -o conftest -m32  
conftestf.f:3.17:

       INTEGER*16 x(2)                                                  
                 1
Error: Old-style type declaration INTEGER*16 not supported at (1)
configure:36664: $? = 1
configure:36681: error: Could not determine size of INTEGER*16
...




Open MPI 1.9:
-------------
...
  $ ../openmpi-1.9a1r27668/configure --prefix=/usr/local/openmpi-1.9_32_cc 
--with-jdk-bindir=/usr/local/jdk1.7.0_07-32/bin 
--with-jdk-headers=/usr/local/jdk1.7.0_07-32/include 
JAVA_HOME=/usr/local/jdk1.7.0_07-32 LDFLAGS=-m32 CC=cc CXX=CC FC=f95 
CFLAGS=-m32 
CXXFLAGS=-m32 -library=stlport4 FCFLAGS=-m32 CPP=cpp CXXCPP=cpp CPPFLAGS= 
CXXCPPFLAGS= C_INCL_PATH= C_INCLUDE_PATH= CPLUS_INCLUDE_PATH= 
OBJC_INCLUDE_PATH= 
OPENMPI_HOME= --enable-cxx-exceptions --enable-mpi-java --enable-heterogeneous 
--enable-opal-multi-threads --enable-mpi-thread-multiple --with-threads=posix 
--with-hwloc=internal --without-verbs --without-udapl 
--with-wrapper-cflags=-m32 
--enable-debug
...
ac_cv_env_CXX_value=CC
ac_cv_env_FCFLAGS_set=set
ac_cv_env_FCFLAGS_value=-m32
ac_cv_env_FC_set=set
ac_cv_env_FC_value=f95
...


Thank you very much for your help.


Kind regards

Siegmar


> On Dec 12, 2012, at 10:33 AM, Siegmar Gross wrote:
> 
> > Hi,
> > 
> > I tried to build openmpi-1.6.4a1r27643 on several platforms
> > (Solaris Sparc, Solaris x86_64, and Linux x86_64) with Solaris
> > Studio C (Sun C 5.12) in 32 and 64 bit mode. "configure" broke
> > on Linux (openSuSE Linux 12.1) for the 32 bit version with the
> > following error:
> > 
> > ...
> > checking if Fortran 77 compiler supports INTEGER*16... yes
> > checking size of Fortran 77 INTEGER*16... configure: error:
> >  Could not determine size of INTEGER*16
> > linpc1 openmpi-1.6.4-Linux.x86_64.32_cc 144 
> > 
> > 
> > I could compile a 32 bit version of openmpi-1.9a1r27668 on the
> > machine without problems.
> > 
> > linpc1 openmpi-1.9-Linux.x86_64.32_cc 148 grep "INTEGER\*16" 
> > log.configure.Linux.x86_64.32_cc
> > checking if Fortran compiler supports INTEGER*16... no
> > linpc1 openmpi-1.9-Linux.x86_64.32_cc 149 
> > 
> > Does anybody have an idea why "configure" broke for
> > openmpi-1.6.4a1r27643 and how I can fix the problem? Thank you
> > very much for any help in advance.
> > 
> > 
> > Kind regards
> > 
> > Siegmar
> > 
> > _______________________________________________
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> 

Reply via email to