Re: The Include Macro

Dave, thanks for the advice. That file was very helpful; I got the plugin to build on my machine. Unfortunately, there are some problems; the plugin works on the examples: show-passes, show-callgraph, and show-docs only. Show-ssa, show-gimple, and the libcpychecker all give seg faults. These seg faults occur regardless of the c code being compiled (I tried several different c programs including one that just prints hello world). For gcc-with python, when I compile the same c code without the plugin (using macports gcc 4.6), I get no errors or warnings. When I built python.so, there were no errors or warnings either. However, when the object files were made, there were a lot of warnings. Additionally, I'm not sure if my usage of libcpychecker was right: I used: ./gcc-with-cpychecker input.c script.py (I took some example code and put it into the main plugin directory). Here are some other things I had to change to build the plugin in addition to the changes listed on the file you sent me: Needs python 2.7 (uses argparse etc.) gcc-with-python needed to be changed to: gcc-mp-4.6 -fplugin=python.so -fplugin-arg-python-script=$@ gcc-python-docs needed to be changed to: ./gcc-with-python examples/show-docs.py test.c You need to have fmemopen.o pre-made: the header and c source I used is available here: http://code.google.com/p/python-tesseract/source/browse/wiki/python-tesse... In the Makefile, the command to build the plugin needs to include fmemopen.o (I got a linking error when I didn't) The Makefile should have fmemopen.c in the source files Also in the Makefile: Python.framework/Versions/2.7/Python does not exist; it should be changed to: /Library/Frameworks/Python.framework/Versions/2.7/Python. I also needed to leave out the arch commands to build it. The full command to build the plugin (python.so) should look like: gcc-mp-4.6 -I/opt/local/lib/gcc46/gcc/x86_64-apple-darwin10/4.6.3/plugin/include -fPIC -fno-strict-aliasing -O2 -Wall -g -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -fno-strict-aliasing -fno-common -dynamic -isysroot /Developer/SDKs/MacOSX10.6.sdk -g -O2 -DNDEBUG -g -O3 -L/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -ldl -framework CoreFoundation -lpython2.7 -u _PyMac_Error /Library/Frameworks/Python.framework/Versions/2.7/Python -undefined dynamic_lookup -shared gcc-python.o gcc-python-attribute.o gcc-python-callbacks.o gcc-python-callgraph.o gcc-python-cfg.o gcc-python-closure.o gcc-python-diagnostics.o gcc-python-function.o gcc-python-gimple.o gcc-python-location.o gcc-python-option.o gcc-python-parameter.o gcc-python-pass.o gcc-python-pretty-printer.o gcc-python-rtl.o gcc-python-tree.o gcc-python-variable.o gcc-python-version.o gcc-python-wrapper.o autogenerated-callgraph.o autogenerated-cfg.o autogenerated-option.o autogenerated-function.o autogenerated-gimple.o autogenerated-location.o autogenerated-parameter.o autogenerated-pass.o autogenerated-pretty-printer.o autogenerated-rtl.o autogenerated-tree.o autogenerated-variable.o util-fmemopen.o fmemopen.o -o python.so I needed to have all the .def files in the directory with the plugin (this may just be something wrong with the macports gcc 4.6). If you want a full copy of the Makefile I used to build the plugin, please let me know. When I run the Makefile, it does not build the test-suite because of the seg faults. I think the problem is in the c source for the plugin because both libcpychecker and gcc-with-python give seg faults (maybe fmemopen problems). I will continue working on the seg fault problem. Do you have any ideas about how to fix the seg faults? At some point, would you want me to make a Mac OSX install package for the plugin? Nick On Mar 21, 2012, at 9:22 PM, David Malcolm wrote: