Sorry, I forgot to show my configure options. ./configure --with-cxx=mpicxx --with-cc=mpicc --with-f77=mpif90 --enable-second --enable-exodus --enable-shared=no
On Mon, Feb 27, 2012 at 8:49 PM, Daniel Vasconcelos < [email protected]> wrote: > With the head version of libmesh I am having problems when trying to make > it: > > ---------------------------------------------- > ------- Building Contributed Packages -------- > ---------------------------------------------- > > --- Building fparser ------------------------- > Compiling C++ (in debug mode) util/bytecoderules_parser.cc... > Linking (in debug mode) > util/bytecoderules_parser.x86_64-apple-darwin11.3.0.dbg.o... > Compiling C++ (in debug mode) util/cpp_compress.cc... > Compiling C++ (in debug mode) util/cpp_compress_main.cc... > Linking (in debug mode) > util/cpp_compress.x86_64-apple-darwin11.3.0.dbg.o... > Creating Bytecode (in debug mode) util/bytecoderules_parser... > Compiling C++ (in debug mode) fparser.cc... > In file included from fparser.cc:1648:0: > extrasrc/fp_opcode_add.inc:58:0: error: unterminated #if > In file included from fparser.cc:1660:0: > extrasrc/fp_opcode_add.inc:69:0: error: unterminated argument list > invoking macro "FP_TRACE_BYTECODE_OPTIMIZATION" > extrasrc/fp_opcode_add.inc:58:0: error: unterminated #if > In file included from fparser.cc:1686:0: > extrasrc/fp_opcode_add.inc:58:0: error: unterminated #if > In file included from fparser.cc:1699:0: > extrasrc/fp_opcode_add.inc:58:0: error: unterminated #if > In file included from fparser.cc:1712:0: > extrasrc/fp_opcode_add.inc:58:0: error: unterminated #if > In file included from fparser.cc:1660:0: > extrasrc/fp_opcode_add.inc: In member function ‘void > FunctionParserBase<Value_t>::AddFunctionOpcode(unsigned int) [with Value_t > = long int]’: > extrasrc/fp_opcode_add.inc:68:16: error: expected primary-expression > before ‘)’ token > extrasrc/fp_opcode_add.inc:68:16: error: expected ‘]’ before ‘)’ token > extrasrc/fp_opcode_add.inc:69:6: error: ‘FP_TRACE_BYTECODE_OPTIMIZATION’ > was not declared in this scope > fparser.cc:1663:1: error: expected ‘;’ before ‘}’ token > fparser.cc:1680:1: error: a template declaration cannot appear at block > scope > fparser.cc:1693:1: error: expected ‘;’ before ‘template’ > fparser.cc:1706:1: error: a template declaration cannot appear at block > scope > fparser.cc:1718:1: error: expected ‘;’ before ‘template’ > fparser.cc:1725:1: error: a template declaration cannot appear at block > scope > fparser.cc:1782:1: error: expected ‘;’ before ‘template’ > fparser.cc:1797:1: error: a template declaration cannot appear at block > scope > fparser.cc:1859:1: error: expected ‘;’ before ‘template’ > fparser.cc:3853:1: error: expected ‘}’ at end of input > extrasrc/fp_opcode_add.inc:60:1: warning: unused variable ‘x’ > [-Wunused-variable] > extrasrc/fp_opcode_add.inc:61:1: warning: unused variable ‘A’ > [-Wunused-variable] > extrasrc/fp_opcode_add.inc:62:1: warning: unused variable ‘y’ > [-Wunused-variable] > extrasrc/fp_opcode_add.inc:63:1: warning: unused variable ‘B’ > [-Wunused-variable] > extrasrc/fp_opcode_add.inc:64:1: warning: unused variable ‘C’ > [-Wunused-variable] > extrasrc/fp_opcode_add.inc:65:1: warning: unused variable ‘D’ > [-Wunused-variable] > fparser.cc:3853:1: error: expected ‘}’ at end of input > extrasrc/fp_opcode_add.inc:65:14: warning: label ‘TailCall_cAbs’ defined > but not used [-Wunused-label] > extrasrc/fp_opcode_add.inc:66:1: error: label ‘Laa’ used but not defined > make[2]: *** [fparser.x86_64-apple-darwin11.3.0.dbg.o] Error 1 > make[1]: *** [all] Error 2 > make: *** > [/Users/daniel/Dev/libmesh-0.7.2/libmesh/lib/x86_64-apple-darwin11.3.0_dbg/libmesh.a] > Error 2 > > On Mon, Feb 27, 2012 at 12:20 PM, Roy Stogner <[email protected]>wrote: > >> >> On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: >> >> This problem also has happened when I tried to run this example in a >>> linux virtual machine. Now I am trying to run it in Mac OS X. >>> >> >> Stranger and stranger... >> >> >> >>> I will checkout the latest version of libmesh from the SVN and if I come >>> up with something I will tell you. >>> >> >> Thanks. >> >> >> >>> Do you thinks this could be a problem due the version of the openmpi >>> or PETSc I am using? >>> >> >> If you've got an mpi stack that requires use of mpirun or mpiexec, >> then you need to set that in a LIBMESH_RUN variable before the >> examples will work. But I don't think that's the problem here; the >> symptom of that is usually a death in MPI init at the start of the >> program. >> >> >> Or even an error during the configuration of libmesh? >>> >> >> Also unlikely... but just for the record, what options did you pass to >> configure? >> >> I still think the only way to get at this is backwards - get to the >> failure point in a debugger (e.g. "LIBMESH_RUN='gdb --args' METHOD=dbg >> make run_examples" and then >> "catch throw"; "run" in gdb) and then see what the stack trace and the >> ifstream flags look like. >> >> Thanks, >> --- >> Roy > > > ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
