[MacPorts] #52016: webkit2-gtk @2.12.3_0: configure fails on 10.6 due to old ruby - requires 1.9 or later

MacPorts noreply at macports.org
Sun Aug 14 19:51:54 PDT 2016


#52016: webkit2-gtk @2.12.3_0: configure fails on 10.6 due to old ruby - requires
1.9 or later
-------------------------------------+-------------------------
  Reporter:  kenneth.f.cunningham@…  |      Owner:  jeremyhu@…
      Type:  defect                  |     Status:  new
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:  2.3.4
Resolution:                          |   Keywords:  snowleopard
      Port:  webkit2-gtk             |
-------------------------------------+-------------------------

Comment (by kenneth.f.cunningham@…):

 And ultimately, success installing webkit2-gtk on snowleopard with libc++.

 In addition to upgrading Ruby as above, the X11 Cursor type conflict can
 be bypassed by using webkit2-gtk +quartz-x11 (and this requires rebuilding
 several of the prerequisites with +quartz-x11 as well).

 That then leads to a minor error with a missing definition for PRId64,
 which is a known bug in webkit
 <<https://bugs.webkit.org/show_bug.cgi?id=156596>

 {{{

 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_webkit2-gtk/webkit2-gtk/work/webkitgtk-2.12.3/Source/WebCore/platform/network/ParsedContentRange.cpp:133:41:
 error: expected ')'
         return String::format("bytes %" PRId64 "-%" PRId64 "/*",
 m_firstBytePosition, m_lastBytePosition);
                                         ^
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_webkit2-gtk/webkit2-gtk/work/webkitgtk-2.12.3/Source/WebCore/platform/network/ParsedContentRange.cpp:133:30:
 note: to match this '('
         return String::format("bytes %" PRId64 "-%" PRId64 "/*",
 m_firstBytePosition, m_lastBytePosition);
                              ^
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_webkit2-gtk/webkit2-gtk/work/webkitgtk-2.12.3/Source/WebCore/platform/network/ParsedContentRange.cpp:134:37:
 error: expected ')'
     return String::format("bytes %" PRId64 "-%" PRId64 "/%" PRId64,
 m_firstBytePosition, m_lastBytePosition, m_instanceLength);
                                     ^
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_webkit2-gtk/webkit2-gtk/work/webkitgtk-2.12.3/Source/WebCore/platform/network/ParsedContentRange.cpp:134:26:
 note: to match this '('
     return String::format("bytes %" PRId64 "-%" PRId64 "/%" PRId64,
 m_firstBytePosition, m_lastBytePosition, m_instanceLength);
                          ^
 2 errors generated.
 }}}

 Which can be fixed with a very simple edit in one file to force the
 definition:

 Source/WebCore/platform/network/ParsedContentRange.cpp
 {{{

 -#if OS(WINDOWS) && !defined(PRId64)
 +#if !defined(PRId64)
  #define PRId64 "lld"
  #endif
 }}}

 and finally the (long) build completes.

 I'll try to put these all together one Portfile diff that might encompass
 this, along with the one very minor source patch.

 Perhaps this up-to-date webkit build might lead to a current browser that
 can run on snowleopard.

 I apologize for lumping the three related webkit2-gtk issues into one
 ticket -- I suspect I should have listed the three issues as separate
 tickets, but I think they'll be repaired with one diff file and they all
 applied to one build on this system so they rather flowed into each other.

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


More information about the macports-tickets mailing list