-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Intl: prepare for ICU 56 bump #3065
Labels
i18n-api
Issues and PRs related to the i18n implementation.
Comments
(by the way, this was caught by the continuous integration of ICU-trunk with Node-master, as discussed at the collaborator's summit.) |
srl295
added a commit
to srl295/node-v0.x-archive
that referenced
this issue
Sep 25, 2015
ICU 56 renamed derb.c to derb.cpp because of C++ yay. This broke the exclusion of "derb.c" when building tools. Solution is to add derb.c AND derb.cpp to exclusion. We don't build the 'derb' tool, so it's fine to list the excluded source twice. Reviewed-By: PR-URL: Fixes: nodejs/node#3065
@mhdawson fyi |
Looks like a false alarm / unclean local build dir. Clean build worked fine. |
srl295
added a commit
that referenced
this issue
Oct 8, 2015
* Exclude `derb.cpp` as well as `derb.c` from Node builds (file was renamed in ICU 56) ICU 56 renamed derb.c to derb.cpp because of C++ yay. This broke the exclusion of "derb.c" when building tools. Solution is to add derb.c AND derb.cpp to exclusion. We don't build the 'derb' tool, so it's fine to list the excluded source twice. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: #3066 Fixes: #3065
This was referenced Sep 17, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Even if we don't yet make ICU 56 default as in #2917 I'd like to make it so that people who manually choose 56 won't get a failure.
A file was renamed from
derb.c
toderb.cpp
and so currently a build issue results in this file not being properly excluded. Since it's not explicitly built, it's fine to just list both the.c
and.cpp
versions in the exclude list.The text was updated successfully, but these errors were encountered: