Hey, 
if I recall correctly you are trying to run this code on stampede @TACC.
I am persuaded that the compiler you are using:
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
is the old 4.4 gcc:

$ /usr/bin/c++ -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla 
--enable-bootstrap --enable-shared --enable-threads=posix 
--enable-checking=release --with-system-zlib --enable-__cxa_atexit 
--disable-libunwind-exceptions --enable-gnu-unique-object 
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk 
--disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre 
--enable-libgcj-multifile --enable-java-maintainer-mode 
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib 
--with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC)

If you have correctly compiled dolfin with the gcc/4.7.1 (which I guess you 
load with module load gcc/4.7.1) you just have to:
export CXX=g++
export CC=gcc

before compiling the demo, both the python and c++ versions.

Best, 


Andrés A. León Baldelli
—
LSU Center for Computation & Technology
2099 Louisiana Digital Media Center



Il giorno 27/giu/2014, alle ore 07:09, Johannes Ring <[email protected]> ha 
scritto:

> Yes, they look okay. What I don't understand is that the flag -std=c++0x is 
> defined in DOLFIN_CXX_FLAGS in DOLFINConfig.cmake and DOLFIN_CXX_FLAGS is 
> added to CMAKE_CXX_FLAGS in the CMakeLists.txt for the demo, but still the 
> flag is not added when compiling the demo. Just to be sure, can you run the 
> following commands in the C++ poisson demo directory?
> 
>   rm -rf build
>   mkdir build
>   cd build
>   cmake ..
>   make VERBOSE=1
> 
> Then post the output from the make command here.
> 
> Johannes
> 
> 
> On Tue, Jun 24, 2014 at 4:32 PM, Sai Rajeshwar <[email protected]> wrote:
> are they fine..  should i reinstall dolfin .
> 
> thanks..
> 
> with regards..
> 
> M. Sai Rajeswar
> M-tech  Computer Technology
> IIT Delhi
> ----------------------------------Cogito Ergo Sum---------
> 
> 
> On Tue, Jun 24, 2014 at 6:24 PM, Sai Rajeshwar <[email protected]> wrote:
> ​
>  CMakeCache.txt
> ​​
>  DOLFINConfig.cmake
> ​
> 
> with regards..
> 
> M. Sai Rajeswar
> M-tech  Computer Technology
> IIT Delhi
> ----------------------------------Cogito Ergo Sum---------
> 
> 
> On Tue, Jun 24, 2014 at 6:01 PM, Johannes Ring <[email protected]> wrote:
> On Tue, Jun 24, 2014 at 1:11 PM, Sai Rajeshwar <[email protected]> wrote:
> >
> > login2$ make
> > [100%] Building CXX object CMakeFiles/demo_poisson.dir/main.cpp.o
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/type_traits:35,
> >                  from /home1/03023/rajeswar/include/dolfin/common/MPI.h:30,
> >                  from
> > /home1/03023/rajeswar/include/dolfin/common/dolfin_common.h:17,
> >                  from /home1/03023/rajeswar/include/dolfin.h:10,
> >                  from
> > /home1/03023/rajeswar/share/dolfin/demo/documented/poisson/cpp/main.cpp:34:
> > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/c++0x_warning.h:31:2:
> > error: #error This file requires compiler and library support for the
> > upcoming ISO C++ standard, C++0x. This support is currently experimental,
> > and must be enabled with the -std=c++0x or -std=gnu++0x compiler options.
> 
> This is the same problem you had with the Python demo, that is, it
> does not include the -std=c++0x flag. Can you attach the
> CMakeCache.txt file in the demo build directory. Please also attach
> DOLFINConfig.cmake (which should be installed in ~/share/dolfin/cmake/
> in your case).
> 
> Johannes
> 
> 
> 
> _______________________________________________
> fenics-support mailing list
> [email protected]
> http://fenicsproject.org/mailman/listinfo/fenics-support

_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to