<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Dear Dune support team,<br><br></div>I am still elaborating to install my dune project on a linux server and I have still problems. The problem is however this time very strange for me.<br>
<br></div>On machine 1 with operating system ubuntu the following packages are installed:<br></div>automake 1.11.2<br></div>autoconf 2.68<br></div>libtool 2.4.2<br></div>openmpi 1.6.1<br></div>ALUGrid 1.52<br>
</div>dune-common rev. 7127<br>dune-geometry rev. 375<br>dune-grid rev. 8798<br></div>dune-istl rev. 1789<br></div>gcc 4.7.1<br><br></div>On this machine my dune code runs perfectly.<br><br></div>On machine 2 with operating system scientific linux the following packages are installed:<br>
automake 1.13<br>
autoconf 2.69<br>
libtool 2.4.2<br>
openmpi 1.6.3<br>
ALUGrid 1.52<br>
dune-common rev. 7127<br>
dune-geometry rev. 375<br>
dune-grid rev. 8798<br>
dune-istl rev. 1789<br>
gcc 4.7.2<br><br></div>However, the same dune code returns an error for this system (the dune modules compile perfectly), which is partly as follows:<br><br>if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-common">desy.de/user/a/afallahi/workspace/dune-common</a> -I/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-geometry">desy.de/user/a/afallahi/workspace/dune-geometry</a> -I/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-grid">desy.de/user/a/afallahi/workspace/dune-grid</a> -I/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-localfunctions">desy.de/user/a/afallahi/workspace/dune-localfunctions</a> -I/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-istl">desy.de/user/a/afallahi/workspace/dune-istl</a> -O3 -g0 --no-strict-aliasing -I/tools/openmpi-1.6.3/include -pthread -DMPIPP_H -DENABLE_MPI=1 -I/tools/ALUGrid-1.52/include -I/tools/ALUGrid-1.52/include/serial -I/tools/ALUGrid-1.52/include/duneinterface -DENABLE_ALUGRID -I/tools/ALUGrid-1.52/include/parallel -I/tools/openmpi-1.6.3/include -pthread -DMPIPP_H -DENABLE_MPI=1 -DWITH_INDEX_SETS -O3 -g0 --no-strict-aliasing -MT dgtd-dgtd.o -MD -MP -MF ".deps/dgtd-dgtd.Tpo" -c -o dgtd-dgtd.o `test -f 'dgtd.cc' || echo './'`dgtd.cc; \<br>
then mv -f ".deps/dgtd-dgtd.Tpo" ".deps/dgtd-dgtd.Po"; else rm -f ".deps/dgtd-dgtd.Tpo"; exit 1; fi<br>In file included from /afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/common/grid.hh:12">desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/common/grid.hh:12</a>,<br>
from /afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid/3d/indexsets.hh:11">desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid/3d/indexsets.hh:11</a>,<br> from /afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid/3d/alugrid.hh:10">desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid/3d/alugrid.hh:10</a>,<br>
from /afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid.hh:9">desy.de/user/a/afallahi/workspace/dune-grid/dune/grid/alugrid.hh:9</a>,<br> from ../config.h:578,<br>
from ../main/dgtd.hh:24,<br> from dgtd.cc:6:<br>/afs/<a href="http://desy.de/user/a/afallahi/workspace/dune-common/dune/common/fvector.hh:20:2">desy.de/user/a/afallahi/workspace/dune-common/dune/common/fvector.hh:20:2</a>: warning: #warning The FieldVector class exports its size by the enum member 'size'. This behavior is deprecated. In the future, 'size' will be a method, which puts it in compliance with the stl conventions. To enable the new behavior (and get rid of this warning), build your Dune with --enable-fieldvector-size-is-method. If you do need the vector size as an enum, use 'dimension'.<br>
../cyrus/signal.hh: In member function 'void Cyrus3d::SignalDataBase::showAll()':<br>../cyrus/signal.hh:640: error: using 'typename' outside of template<br>../cyrus/signal.hh:644: error: using 'typename' outside of template<br>
../cyrus/signal.hh:648: error: using 'typename' outside of template<br>../cyrus/signal.hh:652: error: using 'typename' outside of template<br>../cyrus/signal.hh:656: error: using 'typename' outside of template<br>
../cyrus/excitation.hh: In member function 'Cyrus3d::Excitation<FieldValueType, CoordinateType, dim>* Cyrus3d::ExcitationDataBase<FieldValueType, CoordinateType, dim>::excitation(std::string)':<br>../cyrus/excitation.hh:841: warning: statement is a reference, not call, to function 'exit'<br>
../cyrus/datainput.hh: In function 'std::string Cyrus3d::stringValue(std::string)':<br>../cyrus/datainput.hh:87: error: expected primary-expression before '{' token<br>../cyrus/datainput.hh:87: error: expected ';' before '{' token<br>
../cyrus/datainput.hh:87: error: expected `;' before '}' token<br><br></div><div>This seems to be due to the incorrect standard chosen for this machine. In the first line "g++" should be "g++ -std=c++0x" as in machine 1. I googled and searched throughout the Dune Build howto to find the way to set this in the opts file. However, I could not find any thing. My opt file is pretty simple:<br>
<br>CONFIGURE_FLAGS=" MPICC='/tools/openmpi-1.6.3/bin/mpicc'<br> CXXFLAGS='-O3 -g0 --no-strict-aliasing'<br> CPPFLAGS='-O3 -g0 --no-strict-aliasing'<br>
--enable-parallel<br> --prefix='/tools/cyrus'<br> --with-metis='/tools/metis-5.0.2'<br> --with-alugrid='/tools/ALUGrid-1.52' "<br>
<br></div><div>I tried adding "-std=c++0x" to the CXXFLAGS but it prevents the other dune-modules to compile. My question is do you know the correct way to force the c++0x standard for compiling the code?<br><br>
</div><div>Thank you in advance for your assistance and best regards,<br></div><div>Arya<br></div><div><br><br></div><div><div><div><div><br><br><div><br><div><br></div></div></div></div></div></div></div>