-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Install icu-full when building from source #1719
Comments
As you can see in I tried reading through https://github.com/nodejs/node/wiki/Intl#full-icu-vs-small-icu but nothing popped up. |
Is the |
i assume it’s a bouncing character. As for config files, would they all be relative to the node installation? Or might some be at home dir or machine level? |
Indeed, I did not realise bouncing chars were part of the pasted output. I got puzzled when I saw ICU configuration goes well when I run the same command with Node sources and with homebrew formula on macOS. Is there anything that could be helpful to get down to the root of the problem? |
This is causing issues on Travis because it uses nvm to install Node, and some Node features work differently on Linux under the default ICU: travis-ci/travis-ci#9422 |
@nickmccurdy fwiw, a test like that for number precision is inherently problematic, because precisions are always implementation-dependent - while this issue still needs to be solved in nvm, a better solution for you is to change your test to be robust against varying precisions. |
Thanks, I was using |
I'm also having the same issue. When running:
I get the following output:
Note that running Using Edit: For anyone still looking to solve this issue, I've written up some instructions on how to have multiple versions of node installed on your machine with full ICU support (without the use of |
Interestingly, the ICU download works when I change the following line: with
I can't get my head around why the content of the variable is not received down the line by the PS: I use |
@oncletom ok, this is getting somewhere - what happens if you |
This is the output I get:
I tried replacing the ./configure --prefix="${VERSION_PATH}" $(echo -n $ADDITIONAL_PARAMETERS) && \ This one works too:
$ setopt
alwaystoend
autocd
autopushd
autoresume
nobgnice
nocaseglob
cdablevars
nocheckjobs
noclobber
combiningchars
completeinword
correct
extendedglob
extendedhistory
noflowcontrol
histexpiredupsfirst
histfindnodups
histignorealldups
histignoredups
histignorespace
histsavenodups
histverify
nohup
incappendhistory
interactive
interactivecomments
login
longlistjobs
monitor
nonomatch
pathdirs
promptsubst
pushdignoredups
pushdsilent
pushdtohome
rcquotes
sharehistory
shinstdin
zle When I do switch to bash, additional params works with the original code:
|
Great - that means it’s specific to one of your enabled zsh options. The easiest for me is if you binary search, disabling half of yours, trying again, etc, until you’ve narrowed down which option breaks it - at which point i can wrap the install command in code that disables that option. |
Well, I removed all but 3 $ setopt
interactive
shinstdin
zle I still encounter the error. BUT. It occurred to me the variable is well populated, it works in an I found out the Although by reading I feel the two latest ones are likely to have less/no side-effect on the rest of nvm. |
Unfortunately nvm isn’t bash, it’s posix, and there’s no arrays in posix. My short term plan is to ensure shwordsplit is enabled around that command; if a better option presents itself I’m happy to use it :-) |
@ljharb cool no probs 🙂 Let met know if you need anything else. Happy to help review the fix when you feel like it. |
@oncletom when you have a chance, could you check out ljharb@3fc7b73 ? If that works for you in zsh, I'll merge it. |
@ljharb I just tested it and it's all good 🙂 |
Operating system and version: macOS Sierra
nvm debug
output:nvm ls
output:How did you install
nvm
? (e.g. install script in readme, homebrew): homebrewWhat steps did you perform?
I tried to install node from source to specify additional ICU options.
Install failed. Although I specified either
system-icu
orfull-icu
, the logs refer tosmall-icu
.To install node v8 with full ICU support.
.bashrc
,.bash_profile
,.zshrc
, etc) that modifies thePATH
?The text was updated successfully, but these errors were encountered: