{"action":"closed","issue":{"url":"https://api.github.com/repos/Homebrew/homebrew/issues/44110","labels_url":"https://api.github.com/repos/Homebrew/homebrew/issues/44110/labels{/name}","comments_url":"https://api.github.com/repos/Homebrew/homebrew/issues/44110/comments","events_url":"https://api.github.com/repos/Homebrew/homebrew/issues/44110/events","html_url":"https://github.com/Homebrew/homebrew/issues/44110","id":107231292,"number":44110,"title":"Future Node Icu4c Discussion","user":{"login":"bcomnes","id":166301,"avatar_url":"https://avatars.githubusercontent.com/u/166301?v=3","gravatar_id":"","url":"https://api.github.com/users/bcomnes","html_url":"https://github.com/bcomnes","followers_url":"https://api.github.com/users/bcomnes/followers","following_url":"https://api.github.com/users/bcomnes/following{/other_user}","gists_url":"https://api.github.com/users/bcomnes/gists{/gist_id}","starred_url":"https://api.github.com/users/bcomnes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bcomnes/subscriptions","organizations_url":"https://api.github.com/users/bcomnes/orgs","repos_url":"https://api.github.com/users/bcomnes/repos","events_url":"https://api.github.com/users/bcomnes/events{/privacy}","received_events_url":"https://api.github.com/users/bcomnes/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-09-18T16:07:23Z","updated_at":"2015-09-19T15:49:24Z","closed_at":"2015-09-19T15:49:24Z","body":"So there is this longstanding issue: https://github.com/Homebrew/homebrew/issues/36681\r\n\r\n> So the issue is that the node executable links against libstdc++ because of an archaic deployment target setting.\r\n\r\n> It would be cool if node would link against libc++, but that will require someone to convince upstream.\r\n\r\n```\r\nbret-mbr:~ bret$ otool -L `which node`\r\n/usr/local/bin/node:\r\n\t/usr/local/opt/icu4c/lib/libicui18n.55.dylib (compatibility version 55.0.0, current version 55.1.0)\r\n\t/usr/local/opt/icu4c/lib/libicuuc.55.dylib (compatibility version 55.0.0, current version 55.1.0)\r\n\t/usr/local/opt/icu4c/lib/libicudata.55.1.dylib (compatibility version 55.0.0, current version 55.1.0)\r\n\t/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1153.18.0)\r\n\t/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)\r\n\t/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 104.1.0)\r\n\t/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 283.0.0)\r\n```\r\n\r\nEven in Node 4+, they are building against libstdc++ which presents a potential issue with the homebrew Icu4c which links against libc++.  While there hasn't been a huge amount of direct evidence that this is  a major issue, it still warrants the considerations of the following options:\r\n\r\n1) Stage Icu4c as a resource and staticly build along with node itself. https://github.com/chrmoritz/homebrew/commit/a669d8c7ec4b33ff7f8b0b5e0f184b50c620367e cc @chrmoritz\r\n\r\n2) Link against homebrews Icu4c as a dependency https://github.com/bcomnes/homebrew/commit/309e9b4f61053a864698f82f7318829a1abcd2d8\r\n\r\nBoth seem to work fine.  Long term we can see if we can encourage linking against libc++ upstream but it would be nice to figure something out for now.\r\n\r\ncc @DomT4 @mikemcquaid \r\n\r\n"}}