[MacPorts] #40852: qt4-mac does not build on OS X 10.9 Mavericks or later

[MacPorts]

#40852: qt4-mac does not build on OS X 10.9 Mavericks or later
--------------------------+-------------------------
  Reporter:  kolyosick@…  |      Owner:  michaelld@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.2.99
Resolution:               |   Keywords:  mavericks
      Port:  qt4-mac      |
--------------------------+-------------------------

Comment (by benjamin.seppke@…):

 Next update (last one for today, and hopefully nearly finished): Today I
 tested the former proposed steps a bit further and have to tell you some
 things:

 1. The former patch for bearer is not functional. It compiles but if
 called, it will not work. This is due to the change from NSArray to NSSet.
 NSSet does not support objectAtIndex.. When i call PyQt for example, I get
 2013-10-28 23:08:33.714 Python[15064:890f] -[__NSSetI objectAtIndex:]:
 unrecognized selector sent to instance 0x7ffcd67af970.__ I'll take a
 closer look on this issue tomorrow.

 2. Today I worked on the enabling of WebKit to be built under 10.9. So
 far, it took more hours than I imagined, but it finally works for me now.
 Nearly all the errors are quite easy to fix, although there are quite a
 lot of them. I'll attach all the five new patch-files to this thread after
 this posting. This also requires a new static WebKit library, which I
 borrowed from https://codereview.qt-project.org/#change,69328 . I'll also
 append that lib to this thread

 3. Unfortunately, I could not fix one error in
 src/3rdparty/webkit/Source/WebCore/platform/Timer.cpp. It is just about
 the two calls "pop_heap" and "push_heap" calls, which result in strange
 c++11 errors during compilation. Instead I "fixed it" by commenting the
 lines out, just to see if it's working afterwards. Thus, the patch
 indicating this file is more ore less a temporary workaround and should
 *not* be considered as a patch.

 To conclude, if I see it right, we only need to fix two issues now: The
 bearer Objective-C-code for the new CoreWLAN-api and the c++ code for the
 WebKit's WebCore/platform/Timer.cpp c++ file. I hope to get that done by
 tomorrow, but I'd highly appreciate and be thankful for any kind of
 support or further testing.

 Best wishes,
 Benjamin

-- 
Ticket URL: <https://trac.macports.org/ticket/40852#comment:57>
MacPorts <http://www.macports.org/>
Ports system for OS X