From: shailesh b. <sha...@gm...> - 2012-03-29 13:10:21
|
I have been trying to fix the errors in 'gsco2009-matevz' from so long, but I couldn't fix it. When I run this command 'Swig -python cpp0x_result_of.i', it generates 'cpp0x_result_of_wrap.cxx'. when I compile this command with gcc, it shows me some errors like, checking testcase cpp0x_result_of (with run test) under python cpp0x_result_of_wrap.cxx: In function ‘PyObject* _wrap_test_result(PyObject*, PyObject*)’: cpp0x_result_of_wrap.cxx:2876:42: error: ‘type name’ declared as function returning a function cpp0x_result_of_wrap.cxx:2876:44: error: template argument 1 is invalid cpp0x_result_of_wrap.cxx:2876:52: error: expected initializer before ‘result’ cpp0x_result_of_wrap.cxx:2890:3: error: ‘result’ was not declared in this scope cpp0x_result_of_wrap.cxx:2890:65: error: no matching function for call to ‘test_result_impl(double* (*&)(double), double&)’ cpp0x_result_of_wrap.cxx:2891:15: error: ‘type name’ declared as function returning a function cpp0x_result_of_wrap.cxx:2891:15: error: template argument 1 is invalid cpp0x_result_of_wrap.cxx:2891:15: error: expected ‘)’ before ‘type’ cpp0x_result_of_wrap.cxx:2891:254: error: expected ‘)’ before ‘;’ token make[2]: *** [python_cpp] Error 1 cpp0x_result_of_wrap.cxx is generated by Swig, means that Swig itself is generating files that contains errors. Means this file is not getting properly parsed by Swig. So to remove those errors, where do I have to make changes so that errors can be removed? The only file that I have is( inside test-suite directory) interface file( .i). So where to find the file(source code) that generates _wrap.cxx file. Is it inside the 'gsoc2009_matevz' branch? please reply. shailesh |
From: Vadim Z. <vz...@ze...> - 2012-03-29 13:24:33
|
[Changed the subject to be more descriptive.] On Thu, 29 Mar 2012 18:40:11 +0530 shailesh borkar <sha...@gm...> wrote: sb> I have been trying to fix the errors in 'gsco2009-matevz' from so sb> long, but I couldn't fix it. sb> When I run this command 'Swig -python cpp0x_result_of.i', sb> it generates 'cpp0x_result_of_wrap.cxx'. sb> when I compile this command with gcc, sb> it shows me some errors like, sb> checking testcase cpp0x_result_of (with run test) under python sb> cpp0x_result_of_wrap.cxx: In function ‘PyObject* sb> _wrap_test_result(PyObject*, PyObject*)’: sb> cpp0x_result_of_wrap.cxx:2876:42: error: ‘type name’ declared as sb> function returning a function Shailesh, I know I asked you to post the details of the errors you were getting to the list myself but the key word was "details". It's really impossible to say what the error is (without compiling the branch myself and redoing everything you already did) without knowing what, exactly, is at the line 2876 of this file. Please look at the code generated by SWIG, quote (small) parts of it here if you don't understand what the error is about and at least tell us in which wrapped function does it occur. sb> cpp0x_result_of_wrap.cxx is generated by Swig, means that Swig itself sb> is generating files that contains errors. Means this file is not sb> getting properly parsed by Swig. So to remove those errors, where do sb> I have to make changes so that errors can be removed? That's an excellent question which you're supposed to find the answer to. We're ready to help but it would be great if you could advance at least a little yourself. What have you found during the long time you spent on debugging this? What does the error above (which you presumably looked at) mean? Where does it happen? sb> The only file that I have is( inside test-suite directory) interface sb> file( .i). So where to find the file(source code) that generates sb> _wrap.cxx file. sb> Is it inside the 'gsoc2009_matevz' branch? It's obviously inside gsoc2009_matevz branch as this is the branch you use. And, as I wrote in our IRC exchange, the sources you're interested in are principally Source/CParse/parser.y and the files in Source/SWIG directory. But it's impossible to know where exactly the bug is, you should look at the wrong code and then try to find where does it come from. If you fail to do this, please ask again here but please try to do it yourself first because this is exactly what you'd need to be doing during the GSoC project, hence if you can't do it, it doesn't bode well for your chances of success during it. Regards, VZ |