@abassign: I happen to agree with Thorsten and Torsten on this one, the RSS feeds can be found on sourceforge, e.g. using the wiki template: http://wiki.flightgear.org/Template:Commit_log
Also, please don't get this wrong (no offense intended or taken), but all this complaining is kinda pointless and also proving that we were right in the other thread, i.e. if you cannot fix such trivial cmake-level issues yourself (even if just by disabling the offending tests), you are unlikely to succeed at "implementing Python support in FlightGear" (as per FGPython an propose for Python as an nasal alternative), because you would have to do quite a bit of reading/learning to understand more about cmake and C++ before you should even consider commenting on replacing existing subsystems in SimGear/FlightGear.
I am just saying this so clearly, because you put quite a bit of energy into your postings/drawings in that other thread, to make us believe that you were serious about that, and at least bugman and myself offered our support and help to get you started with all this - and apparently, you are not even remotely in a position to deal with trivial build issues, which tells us that you should not have made certain (all) postings in the other thread, i.e. you were not just wasting your own time, but also our's. So if you were serious about wanting Python in FlightGear, you would ensure that we allocate our time better, to ensure that our postings actually bear fruits.