strigi @0.7.8_13: error: unknown type name 'char16_t'

[tehcog (tehcog)]

Please see attached main.log

Nov 18 15:14:29 xxXXxx --->  Attempting to fetch strigi-0.7.8_13.darwin_13.x86_64.tbz2 from http://aus.us.packages.macports.org/macports/packages/strigi
Nov 18 15:14:29 xxXXxx --->  Verifying checksums for strigi
Nov 18 15:14:29 xxXXxx --->  Extracting strigi
Nov 18 15:14:30 xxXXxx --->  Applying patches to strigi
Nov 18 15:14:30 xxXXxx --->  Configuring strigi
Nov 18 15:14:40 xxXXxx --->  Building strigi
Nov 18 15:14:53 xxXXxx Error: Failed to build strigi: command execution failed
Nov 18 15:14:53 xxXXxx Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_strigi/strigi/main.log for details.

[tehcog (tehcog)]

main.log

[ryandesign (Ryan Carsten Schmidt)]

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 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.

[jmroot (Joshua Root)]

In 3405b5589e4096490761bf7ccce27b0e9e8c95c9/macports-ports (master):

strigi: revert icu workaround

See: #59723

[jmroot (Joshua Root)]

In 3f144b1ee9d5015b65183b6a38c34e631e026c9c/macports-ports (master):

icu: don't use char16_t when C++ API is hidden

This should allow C++ dependents to build in C++98 mode as long as they
only use the C API.

Fixes: #59723