> But with your output above, my first guess would be that the linker just > isn't finding the gcc files to link against. It might help if you showed > the command line that generated that output, or set a verbose option on > it and see where it's looking.
I' not sure how to make verbose - so I've turned -debug=v flag on in make command: make --debug=v 2>make_log.txt 1>&2 Result is here: http://www.geocities.com/tapika/make_log.txt > I just have the hg tip of dehydra, and I just did 'grep global_namespace > *.h *.c' in the dehydra source dir. Ok, will try to pick up the latest one. > I don't understand the question. It's irrelevant, I've found some answers from documentation to which you gave me a link. > There exists 6 functions which are called between gcc and dehydra. Is > > there any > > description about these functions ? May be you can describe their call > > order and parameters > > shortly ? > > Seehttp://www.gccsummit.org/2008/gcc-2008-proceedings.pdf, page 30. Thanks - that was really useful link. Now my head is bit spinning of information I've just absorved. :) Design desicions are quite important to me look through as well. If you're intrested - zipped ppt (windows/office) slides can be found from the same place as make_log. I'm looking for a way not only to reverse engineere source codes into trees (like gcc / dehydra does) but to be able to produce source code out of that tree as well. CIL link which your document mentiones is one approach to source code regeneration, however new language always bit scares me. No matter how advanced it is. If you can give me any practical compilation assitance with cygwin, it would be great. _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
