From: Daniel V. <las...@gm...> - 2012-02-27 04:52:16
|
I am trying to run the libmesh examples and when I try to run ex1 in debug mode I receive the following error: Compiling C++ (in debug mode) ex1.C... Linking ex1-dbg... *************************************************************** * Running Example ./ex1-dbg -d 3 ../../reference_elements/3D/one_hex27.xda [-o output.xda] *************************************************************** Assertion `in->good()' failed. [0] src/utils/xdr_cxx.C, line 635, compiled Feb 27 2012 at 01:28:18 terminate called after throwing an instance of 'libMesh::LogicError' what(): Error in libMesh internal logic [MacBook-Pro-de-Daniel:07324] *** Process received signal *** [MacBook-Pro-de-Daniel:07324] Signal: Abort trap: 6 (6) [MacBook-Pro-de-Daniel:07324] Signal code: (0) [MacBook-Pro-de-Daniel:07324] [ 0] 2 libsystem_c.dylib 0x00007fff9604ecfa _sigtramp + 26 [MacBook-Pro-de-Daniel:07324] *** End of error message *** make[2]: *** [run] Abort trap: 6 make[1]: *** [run] Error 1 make: *** [run_examples] Error 2 Any clue? |
From: Roy S. <roy...@ic...> - 2012-02-27 06:35:15
|
On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: > *************************************************************** > * Running Example ./ex1-dbg -d 3 ../../reference_elements/3D/one_hex27.xda > [-o output.xda] > *************************************************************** > > Assertion `in->good()' failed. > [0] src/utils/xdr_cxx.C, line 635, compiled Feb 27 2012 at 01:28:18 Very strange. It's complaining about an I/O failure in the middle of reading a trivial input mesh file. I/O failures like that can happen if the input file is corrupted in some way, but nothing in reference_elements/ should be breaking like that. There's no way anyone's going to be able to reproduce this problem (if the first thousand times we ran ex1 didn't break, #1001 won't either), but if you want to dig up more information (a stack trace, whether in->bad() or in->fail() is true, etc) we might be able to help diagnose and fix it. It looks like you're using libMesh 0.7.2? Would you see if a similar error occurs for you with the svn version? Thanks, --- Roy |
From: Daniel V. <las...@gm...> - 2012-02-27 10:02:03
|
Yes, I am actually making use of libmesh 0.7.2. 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. I will checkout the latest version of libmesh from the SVN and if I come up with something I will tell you. Do you thinks this could be a problem due the version of the openmpi or PETSc I am using? Or even an error during the configuration of libmesh? Best regards, Daniel. On Mon, Feb 27, 2012 at 3:35 AM, Roy Stogner <roy...@ic...>wrote: > > On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: > > ******************************************************************* >> * Running Example ./ex1-dbg -d 3 ../../reference_elements/3D/** >> one_hex27.xda >> [-o output.xda] >> ******************************************************************* >> >> Assertion `in->good()' failed. >> [0] src/utils/xdr_cxx.C, line 635, compiled Feb 27 2012 at 01:28:18 >> > > Very strange. It's complaining about an I/O failure in the middle of > reading a trivial input mesh file. I/O failures like that can happen > if the input file is corrupted in some way, but nothing in > reference_elements/ should be breaking like that. There's no way > anyone's going to be able to reproduce this problem (if the first > thousand times we ran ex1 didn't break, #1001 won't either), but if > you want to dig up more information (a stack trace, whether in->bad() > or in->fail() is true, etc) we might be able to help diagnose and fix > it. > > It looks like you're using libMesh 0.7.2? Would you see if a similar > error occurs for you with the svn version? > > Thanks, > --- > Roy > |
From: Roy S. <roy...@ic...> - 2012-02-27 15:20:47
|
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 |
From: Daniel V. <las...@gm...> - 2012-02-27 23:49:32
|
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 <roy...@ic...>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 |
From: Daniel V. <las...@gm...> - 2012-02-27 23:51:07
|
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 < las...@gm...> 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 <roy...@ic...>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 > > > |
From: Roy S. <roy...@ic...> - 2012-02-28 00:00:28
|
On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: > With the head version of libmesh I am having problems when trying to make it: Also weird, but let's look at the possible problem in libMesh first and get back to the possible problem in a third party package later. Try adding "--disable-fparser" to your configure line to disable building fparser. --- Roy > ---------------------------------------------- > ------- 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 |
From: Daniel V. <las...@gm...> - 2012-02-28 00:10:01
|
Weird, now it passed but I used the following configure: ./configure --enable-mpi --enable-second --enable-exodus --enable-shared=no I will try what you said. On Mon, Feb 27, 2012 at 9:00 PM, Roy Stogner <roy...@ic...>wrote: > > On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: > > With the head version of libmesh I am having problems when trying to make >> it: >> > > Also weird, but let's look at the possible problem in libMesh first and get > back to the possible problem in a third party package later. Try > adding "--disable-fparser" to your configure line to disable building > fparser. > --- > Roy > > > ------------------------------**---------------- >> ------- 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 >> > |
From: Daniel V. <las...@gm...> - 2012-02-28 00:13:01
|
Configure complains that --disable-fparser is a unrecognized option. On Mon, Feb 27, 2012 at 9:09 PM, Daniel Vasconcelos < las...@gm...> wrote: > Weird, now it passed but I used the following configure: > > ./configure --enable-mpi --enable-second --enable-exodus --enable-shared=no > > I will try what you said. > > On Mon, Feb 27, 2012 at 9:00 PM, Roy Stogner <roy...@ic...>wrote: > >> >> On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: >> >> With the head version of libmesh I am having problems when trying to >>> make it: >>> >> >> Also weird, but let's look at the possible problem in libMesh first and >> get >> back to the possible problem in a third party package later. Try >> adding "--disable-fparser" to your configure line to disable building >> fparser. >> --- >> Roy >> >> >> ------------------------------**---------------- >>> ------- 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 >>> >> > |
From: Daniel V. <las...@gm...> - 2012-02-29 02:06:06
|
Now the examples are running. I have recompiled with another compiler and it worked. However, I am facing a new problem while trying to run my code. bash-3.2$ mpirun -n 1 run-dbg -of results_cyl_r1 -amr 1 -ri 2 -mf cylinder_refec.xda -dt 1000 wi 100 -gr av 0 -pc_ty pe bjacobi -sub_pc_type ilu -sub_pc_factor_levels 1 -sub_pc_factor_shift_nonzero *** Warning, This code is deprecated, and likely to be removed in future library versions! src/base/libmesh.C, line 558, compiled Feb 28 2012 at 22:08:02 *** ERROR: cannot locate specified file: cylinder_refec.xda [0] src/mesh/unstructured_mesh.C, line 490, compiled Feb 28 2012 at 22:10:53 terminate called throwing an exception[MacBook-Pro-de-Daniel:00707] *** Process received signal *** [MacBook-Pro-de-Daniel:00707] Signal: Abort trap: 6 (6) [MacBook-Pro-de-Daniel:00707] Signal code: (0) [MacBook-Pro-de-Daniel:00707] [ 0] 2 libsystem_c.dylib 0x00007fff8b31dcfa _sigtramp + 26 [MacBook-Pro-de-Daniel:00707] [ 1] 3 ??? 0x0000000000000000 0x0 + 0 [MacBook-Pro-de-Daniel:00707] [ 2] 4 libc++abi.dylib 0x00007fff8d5ce7bc abort_message + 214 [MacBook-Pro-de-Daniel:00707] [ 3] 5 libc++abi.dylib 0x00007fff8d5cbfcf _Z17default_terminatev + 28 [MacBook-Pro-de-Daniel:00707] [ 4] 6 run-dbg 0x000000010ed8f54d _ZN7libMesh25libmesh_terminate_handlerEv + 13 [MacBook-Pro-de-Daniel:00707] [ 5] 7 libc++abi.dylib 0x00007fff8d5cc001 _Z19safe_handler_callerPFvvE + 11 [MacBook-Pro-de-Daniel:00707] [ 6] 8 libc++abi.dylib 0x00007fff8d5cc05c __cxa_bad_typeid + 0 [MacBook-Pro-de-Daniel:00707] [ 7] 9 libc++abi.dylib 0x00007fff8d5cd152 _Z23__gxx_exception_cleanup19_Unwind_Reason_CodeP17_Unwind_Exception + 0 [MacBook-Pro-de-Daniel:00707] [ 8] 10 run-dbg 0x000000010f3e4145 _ZN7libMesh16UnstructuredMesh4readERKSsPNS_8MeshDataEb + 2195 [MacBook-Pro-de-Daniel:00707] [ 9] 11 run-dbg 0x000000010ecf8746 main + 4182 [MacBook-Pro-de-Daniel:00707] [10] 12 run-dbg 0x000000010ece0ba4 start + 52 [MacBook-Pro-de-Daniel:00707] *** End of error message *** -------------------------------------------------------------------------- mpirun noticed that process rank 0 with PID 707 on node MacBook-Pro-de-Daniel.local exited on signal 6 (Abort trap: 6). -------------------------------------------------------------------------- Any ideas? Regards, Daniel. On Mon, Feb 27, 2012 at 9:12 PM, Daniel Vasconcelos < las...@gm...> wrote: > Configure complains that --disable-fparser is a unrecognized option. > > > On Mon, Feb 27, 2012 at 9:09 PM, Daniel Vasconcelos < > las...@gm...> wrote: > >> Weird, now it passed but I used the following configure: >> >> ./configure --enable-mpi --enable-second --enable-exodus >> --enable-shared=no >> >> I will try what you said. >> >> On Mon, Feb 27, 2012 at 9:00 PM, Roy Stogner <roy...@ic...>wrote: >> >>> >>> On Mon, 27 Feb 2012, Daniel Vasconcelos wrote: >>> >>> With the head version of libmesh I am having problems when trying to >>>> make it: >>>> >>> >>> Also weird, but let's look at the possible problem in libMesh first and >>> get >>> back to the possible problem in a third party package later. Try >>> adding "--disable-fparser" to your configure line to disable building >>> fparser. >>> --- >>> Roy >>> >>> >>> ------------------------------**---------------- >>>> ------- 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 >>>> >>> >> > |