镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

missing #include <unicode/ustring.h> #11753

Description

@srl295
  • Subsystem: core/deps

An ICU header was missing from the #includes. This works on current ICU, but fails later when an indirect dependency changes.

diff --git a/deps/v8/src/runtime/runtime-i18n.cc b/deps/v8/src/runtime/runtime-i18n.cc
index 75e0952..c923c17 100644
--- a/deps/v8/src/runtime/runtime-i18n.cc
+++ b/deps/v8/src/runtime/runtime-i18n.cc
@@ -42,6 +42,7 @@
 #include "unicode/unistr.h"
 #include "unicode/unum.h"
 #include "unicode/uversion.h"
+#include "unicode/ustring.h"
 
 
 namespace v8 {
diff --git a/src/node_i18n.cc b/src/node_i18n.cc
index b337456..fab594c 100644
--- a/src/node_i18n.cc
+++ b/src/node_i18n.cc
@@ -43,6 +43,7 @@
 #include <unicode/ulocdata.h>
 #include <unicode/uvernum.h>
 #include <unicode/uversion.h>
+#include <unicode/ustring.h>
 
 #ifdef NODE_HAVE_SMALL_ICU
 /* if this is defined, we have a 'secondary' entry point.

Activity

  1. added
    i18n-apiIssues and PRs related to Node.js internationalization support.
    on Mar 8, 2017
  2. self-assigned this
    on Mar 8, 2017
  3. srl295 commented on Mar 8, 2017

    @srl295
    MemberAuthor

    The second is a v8 patch.

  4. srl295 commented on Mar 27, 2017

    @srl295
    MemberAuthor
    • v8 changes above still don't seem to have landed in node HEAD. Filed CrBug:6173
  5. jungshik commented on Mar 29, 2017

    @jungshik

    https://chromium.googlesource.com/v8/v8/+/5.9.35 is the first v8 release with the v8-side fix. Can Node head roll v8 to that version or later, instead (while rolling ICU to 59) ?

  6. srl295 commented on Mar 29, 2017

    @srl295
    MemberAuthor

    @jungshik will investigate that- the back port would allow older nodes to support newer icu though.

  7. MylesBorins commented on Apr 17, 2017

    @MylesBorins
    Contributor

    @srl295 should this be backported to v6.x?

  8. srl295 commented on Apr 18, 2017

    @srl295
    MemberAuthor

    @MylesBorins it doesn't hurt… it could backport to v0.12 for that matter… however, without the (trivial) v8 patch, it's not going to work in previous versions.

    So yes, it would probably be a good idea to back port it.

  9. srl295 commented on Apr 18, 2017

    @srl295
    MemberAuthor

    re v8 5.9.35: #11827

  10. srl295 commented on May 8, 2017

    @srl295
    MemberAuthor

    For the record: This issue was fixed by a v8 bump in 60d1aac specifically 60d1aac#diff-df47c9a27158d9fcec0511ec405f9172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

i18n-apiIssues and PRs related to Node.js internationalization support.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions