[mpich-discuss] problems with mpich2 configure

jaharvey at chem.umass.edu jaharvey at chem.umass.edu
Tue Jan 12 21:41:49 CST 2010


This is getting a little off topic but doesn't GCC contain G++ no?

Jacob

On Tue, Jan 12, 2010 at 10:29 PM, Pavan Balaji <balaji at mcs.anl.gov> wrote:


     You need a C++ compiler (e.g., g++), if you plan to use C++ programs.
     gcc is a C compiler.

     If you don't need C++, you can just do a configure --disable-cxx, as
     Dave pointed out.

      -- Pavan

     On 01/12/2010 07:38 PM, jaharvey at chem.umass.edu wrote:
     > Would a re-install of GCC fix this problem?
     >
     > Jacob
     >
     > On Tue, Jan 12, 2010 at 5:43 PM, Dave Goodell  
<goodell at mcs.anl.gov> wrote:
     >
     >     It looks like your C++ compiler installation isn't in the best shape
     > (see the quoted passage at the bottom of this mail for an example).  If
     > you don't need C++ support in your mpich2 installation you can configure
     > with --disable-cxx. Otherwise I would work on getting your C++ compiler
     > working on simple programs before attempting to build mpich2.
     >
     >     -Dave
     >
     >     -------8<-------
     >     configure:12111: checking whether C++ compiler works with string
     >     configure:12145: c++ -c -m64  -I/opt/src/mpich2-1.2.1/src/openpa/src
     > -I/opt/src/mpich2-1.2.1/src/openpa/src conftest.cpp >&5
     >     In file included from conftest.cpp:29:
     >
     >  
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../include/c++/3.4.6/string:45:28:
     > bits/c++config.h: No such file or directory
     >     In file included from
     >  
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../include/c++/3.4.6/bits/stl_algobase.h:70,
     >
     >                     from
     >  
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../include/c++/3.4.6/bits/char_traits.h:46,
     >
     >                     from
     >  
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../include/c++/3.4.6/string:47,
     >
     >                     from conftest.cpp:29:
     >     -------8<-------
     >     [trimming lots more error output from the same test]
     >     -------8<-------
     >     configure:12152: $? = 1
     >     configure: failed program was:
     >     | /* confdefs.h.  */
     >     | #define PACKAGE_NAME ""
     >     | #define PACKAGE_TARNAME ""
     >     | #define PACKAGE_VERSION ""
     >     | #define PACKAGE_STRING ""
     >     | #define PACKAGE_BUGREPORT ""
     >     | #define USE_SMP_COLLECTIVES 1
     >     | #define HAVE_ERROR_CHECKING MPID_ERROR_LEVEL_ALL
     >     | #define MPICH_ERROR_MSG_LEVEL MPICH_ERROR_MSG_ALL
     >     | #define USE_LOGGING MPID_LOGGING_NONE
     >     | #define HAVE_RUNTIME_THREADCHECK 1
     >     | #define MPICH_THREAD_LEVEL MPI_THREAD_MULTIPLE
     >     | #define USE_THREAD_IMPL MPICH_THREAD_IMPL_GLOBAL_MUTEX
     >     | #define MPIU_THREAD_GRANULARITY MPIU_THREAD_GRANULARITY_GLOBAL
     >     | #define MPIU_HANDLE_ALLOCATION_METHOD MPIU_HANDLE_ALLOCATION_MUTEX
     >     | #define MPIU_THREAD_REFCOUNT MPIU_REFCOUNT_NONE
     >     | #define HAVE_ROMIO 1
     >     | #define HAVE__FUNC__ /**/
     >     | #define HAVE__FUNCTION__ /**/
     >     | #define HAVE_PRAGMA_WEAK 1
     >     | #define USE_WEAK_SYMBOLS 1
     >     | #define HAVE_MULTIPLE_PRAGMA_WEAK 1
     >     | #define HAVE_LONG_LONG 1
     >     | #define F77_NAME_LOWER_2USCORE 1
     >     | #define STDCALL
     >     | #define HAVE_MPI_F_INIT_WORKS_WITH_C 1
     >     | #define HAVE_FORTRAN_BINDING 1
     >     | /* end confdefs.h.  */
     >     | #include <string>
     >     | int
     >     | main ()
     >     | {
     >     | return 0;
     >     |   ;
     >     |   return 0;
     >     | }
     >     configure:12173: result: no
     >     configure:12176: WARNING: The C++ compiler c++ cannot compile a
     > program containing the <string> header - this may indicate a problem
     > with the C++ installation.  Consider configuing with --disable-cxx
     >     -------8<-------
     >
     >
     >
     >     On Jan 12, 2010, at 4:21 PM, jaharvey at chem.umass.edu wrote:
     >
     >         Dear all,
     >
     >         Here is my config.log file. Looks like I got errors is a few
     > places but I'm not sure which ones are the offending ones.
     >
     >         Jacob
     >
     >         On Tue, Jan 12, 2010 at 5:08 PM, Dave Goodell
     > <goodell at mcs.anl.gov> wrote:
     >
     >           Hi Jacob, can you also send your config.log?  Configure
     > doesn't think that your C++ compiler is in the best shape, but the exact
     > error messages will be contained in the config.log.
     >
     >           -Dave
     >
     >
     >           On Jan 12, 2010, at 3:55 PM, jaharvey at chem.umass.edu wrote:
     >
     >               Dear MPICH2 community,
     >
     >               I am trying to install MPICH2-1.2.1 on my 26 node cluster
     > running CentOS. I want to compile two versions of MPICH2-1.2.1, one for
     > 64 bit machines and the other for 32 bit machines. So for the 64 bit
     > machines I have given the following command:
     >
     >               ./configure --prefix=/opt/mpich2-1.2.1-i86 CFLAGS=-m64
     > FFLAGS=-m64 F90FLAGS=-m64 CXXFLAGS=-m64 2>&1 | tee c.txt
     >
     >               However, when I run this the configuration process ends
     > abruptly with the following errors:
     >
     >               configure: error: C++ compiler
     > /opt/src/mpich2-1.2.1/bin/mpicxx  has neither iostream nor iostream.h.
     >               configure: error: ./configure failed for test/mpi
     >
     >               I am indeed on a 64 bit machine when running ./configure.
     > I have attached my c.txt file. Any help would be greatly appreciated.
     >
     >               Jacob Harvey
     >               <c.txt>_______________________________________________
     >               mpich-discuss mailing list
     >               mpich-discuss at mcs.anl.gov
     >               https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
     >
     >
     >           _______________________________________________
     >           mpich-discuss mailing list
     >           mpich-discuss at mcs.anl.gov
     >           https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
     >
     >
     >
     >         <config.log>_______________________________________________
     >
     >         mpich-discuss mailing list
     >         mpich-discuss at mcs.anl.gov
     >         https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
     >
     >
     >     _______________________________________________
     >     mpich-discuss mailing list
     >     mpich-discuss at mcs.anl.gov
     >     https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
     >
     > _______________________________________________
     > mpich-discuss mailing list
     > mpich-discuss at mcs.anl.gov
     > https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

     --
     Pavan Balaji
     http://www.mcs.anl.gov/~balaji
     _______________________________________________
     mpich-discuss mailing list
     mpich-discuss at mcs.anl.gov
     https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss


More information about the mpich-discuss mailing list