Please be patient with these types of issues(build related) and Jira. We do appreciate that you filed this problem but its very easy for these issues to be missed or overlooked for periods of time do to priority(I'm sure you can understand how difficult a large project can be accross many platforms) but they will not be lost which is the important part. Combining duplicate issues is also difficult, like with this issue I happened to remember that I saw an issue last fall that resembled this one so I went and hunted it down and posted the reference to this list but I missed yours which of course was not intentional.
All of the above are fair points, but what I can't really get my head around is that this particular issue has been gathering dust for the best part of a month and at the same time at least two of the people raising it (myself and Alexsey) proposed a ready-made solution, which is very easy to implement and integrate into the source tree - all that needs to be done is for the path of the original patch to be changed and the appropriate "patch" command line executable to be amended - that is all there is to this, not really rocket science is it? If you do not believe me, look at what I suggested (and attached as a correction patch) in http://jira.freeswitch.org/browse/FS-3923