[MacPorts] #59723: strigi @0.7.8_13: error: unknown type name 'char16_t' (was: strigi @0.7.8_13 fails to build on mavericks)

MacPorts noreply at macports.org
Tue Nov 19 16:39:48 UTC 2019


#59723: strigi @0.7.8_13: error: unknown type name 'char16_t'
---------------------+--------------------
  Reporter:  tehcog  |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.6.2
Resolution:          |   Keywords:
      Port:  strigi  |
---------------------+--------------------
Changes (by ryandesign):

 * cc: ryandesign, landonf (added)


Comment:

 The log says:

 {{{
 :info:build In file included from
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_strigi/strigi/work/strigi-0.7.8/libstreamanalyzer/lib/helperanalyzers/saxhelperanalyzer.h:26:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/SAX2.h:18:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/parser.h:810:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/encoding.h:31:
 :info:build In file included from /opt/local/include/unicode/ucnv.h:52:
 :info:build In file included from
 /opt/local/include/unicode/ucnv_err.h:88:
 :info:build In file included from /opt/local/include/unicode/utypes.h:38:
 :info:build /opt/local/include/unicode/umachine.h:376:13: error: unknown
 type name 'char16_t'
 :info:build     typedef char16_t UChar;
 :info:build             ^
 :info:build In file included from
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_strigi/strigi/work/strigi-0.7.8/libstreamanalyzer/lib/helperanalyzers/odfcontenthelperanalyzer.cpp:22:
 :info:build In file included from
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_strigi/strigi/work/strigi-0.7.8/libstreamanalyzer/lib/helperanalyzers/odfcontenthelperanalyzer.h:26:
 :info:build In file included from
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_strigi/strigi/work/strigi-0.7.8/libstreamanalyzer/lib/helperanalyzers/saxhelperanalyzer.h:26:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/SAX2.h:18:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/parser.h:810:
 :info:build In file included from
 /opt/local/include/libxml2/libxml/encoding.h:31:
 :info:build In file included from /opt/local/include/unicode/ucnv.h:53:
 :info:build In file included from /opt/local/include/unicode/uenum.h:23:
 :info:build /opt/local/include/unicode/localpointer.h:71:51: warning:
 deleted function definitions are a C++11 extension [-Wc++11-extensions]
 :info:build     static void* U_EXPORT2 operator new(size_t) = delete;
 :info:build                                                   ^
 }}}

 It's the same problem we've seen with countless other ports since the icu
 65 upgrade. This port uses libxml2, which uses icu, which now requires
 C++11, therefore this port now requires C++11.

 Landon tried to [changeset:4b2130b86a1df970ef1a83514e533a6a1e5d140d
 /macports-ports fix it a different way]. Landon, do you think there is a
 way to make this port (and others that use icu through libxml2) not
 require C++11? With other ports, so far, we've just been accepting the
 need for C++11 and writing `compiler.cxx_standard 2011`. Unless you have
 another idea, that's what I plan to do here too and revert your previous
 change.

-- 
Ticket URL: <https://trac.macports.org/ticket/59723#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list