-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intl: VS2015: workaround ICU VS2015 failure? #2279
Comments
argh, 2015 is live now, it'd be a shame to have this as the only blocker. is it possible to say something like "to build with VS2015 you must disable icu completely" or is it broken no matter how we look at it? |
This is true at the moment. Sorry, I missed the scope of this issue before. |
Working on a repro. Is the icu lib itself that fails to build or does it fail at link time? We could change the download process to overwrite ufile.c from with a version from trunk (but at that point it would be better to commit it in our repo somewhere), or we could hack-define those missing functions somewhere else either in node or with an additional file for the icu library. |
Getting this error:
..which is at compile time, so my idea of defining the missing functions somewhere else won't help. We should probably hack the build to use a different version of ufile.c then. |
@orangemocha yes, that's the error. The particular function gets treated as "undefined assuming function returning int", and then somehow has a problem subscripting an int. I/we/you can snag the |
@orangemocha thanks for the discussion. I will open a PR here for a workaround. |
oops, was looking for the Intl label! |
The particular ufile.c is from http://bugs.icu-project.org/trac/changeset/37704 and should be OK for ICU 54 and 55. Also, adds general mechanism for floating patches on top of ICU. Fixes: #2279 PR-URL: #2283 Reviewed-By: João Reis <reis@janeasystems.com>
Fixed by 4c06515. |
The particular ufile.c is from http://bugs.icu-project.org/trac/changeset/37704 and should be OK for ICU 54 and 55. Also, adds general mechanism for floating patches on top of ICU. Fixes: #2279 PR-URL: #2283 Reviewed-By: João Reis <reis@janeasystems.com>
This change is a backport of nodejs/node@4c06515. Original commit message: The particular ufile.c is from http://bugs.icu-project.org/trac/changeset/37704 and should be OK for ICU 54 and 55. Also, adds general mechanism for floating patches on top of ICU. Fixes: nodejs/node#2279 PR-URL: nodejs/node#2283 Reviewed-By: João Reis <reis@janeasystems.com> Fixes: #25792 PR-URL: #25804 Reviewed-By: João Reis <reis@janeasystems.com>
This change is a backport of nodejs/node@4c06515. Original commit message: The particular ufile.c is from http://bugs.icu-project.org/trac/changeset/37704 and should be OK for ICU 54 and 55. Also, adds general mechanism for floating patches on top of ICU. Fixes: nodejs/node#2279 PR-URL: nodejs/node#2283 Reviewed-By: João Reis <reis@janeasystems.com> Fixes: nodejs#25792 PR-URL: nodejs#25804 Reviewed-By: João Reis <reis@janeasystems.com>
ICU (which provides
Intl
) failed under VS2015 in the same way and for the same reason as openssl in #478. Should we try to workaround?I already committed a fix to IcuBug:11689, scheduled for release in a couple of months with ICU 56. If we hit this issue earlier, it looks like we could just pull a copy of
ufile.c
from ICU trunk on top of the downloaded ICU.Just filing this for reference.
@rvagg @orangemocha
The text was updated successfully, but these errors were encountered: