Nvm: node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by node)

[VictorioBerra]

• Operating system and version:
  Raspbian GNU/Linux 8 (jessie)

• nvm debug output:
  

  
  

  nvm --version: v0.34.0
  $SHELL: /bin/bash
  $SHLVL: 1
  $HOME: /home/pi
  $NVM_DIR: '$HOME/.nvm'
  $PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
  $PREFIX: ''
  $NPM_CONFIG_PREFIX: ''
  $NVM_NODEJS_ORG_MIRROR: ''
  $NVM_IOJS_ORG_MIRROR: ''
  shell version: 'GNU bash, version 4.3.30(1)-release (arm-unknown-linux-gnueabihf)'
  uname -a: 'Linux 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux'
  OS version: Raspbian GNU/Linux 8
  curl: /usr/bin/curl, curl 7.38.0 (arm-unknown-linux-gnueabihf) libcurl/7.38.0 OpenSSL/1.0.1t zlib/1.2.8 libidn/1.29 libssh2/1.4.3 librtmp/2.3
  wget: /usr/bin/wget, GNU Wget 1.16 built on linux-gnueabihf.
  git: /usr/bin/git, git version 2.1.4
  grep: /bin/grep (grep --color=auto), grep (GNU grep) 2.20
  awk: not an option: --version
  awk: /usr/bin/awk,
  sed: /bin/sed, sed (GNU sed) 4.2.2
  cut: /usr/bin/cut, cut (GNU coreutils) 8.23
  basename: /usr/bin/basename, basename (GNU coreutils) 8.23
  rm: /bin/rm, rm (GNU coreutils) 8.23
  mkdir: /bin/mkdir, mkdir (GNU coreutils) 8.23
  xargs: /usr/bin/xargs, xargs (GNU findutils) 4.4.2
  nvm current: none
  which node:
  which iojs:
  which npm:
  npm config get prefix: -su: npm: command not found
  npm root -g: -su: npm: command not found
  

• nvm ls output:
  

  
  

  pi@mervin-pi:~ $ nvm ls
          v7.7.2
          v12.2.0
  default -> node (-> v12.2.0)
  node -> stable (-> v12.2.0) (default)
  stable -> 12.2 (-> v12.2.0) (default)
  iojs -> N/A (default)
  unstable -> N/A (default)
  lts/* -> lts/dubnium (-> N/A)
  lts/argon -> v4.9.1 (-> N/A)
  lts/boron -> v6.17.1 (-> N/A)
  lts/carbon -> v8.16.0 (-> N/A)
  lts/dubnium -> v10.15.3 (-> N/A)
  pi@mervin-pi:~ $ nvm ls
          v7.7.2
          v12.2.0
  default -> node (-> v12.2.0)
  node -> stable (-> v12.2.0) (default)
  stable -> 12.2 (-> v12.2.0) (default)
  iojs -> N/A (default)
  unstable -> N/A (default)
  lts/* -> lts/dubnium (-> N/A)
  lts/argon -> v4.9.1 (-> N/A)
  lts/boron -> v6.17.1 (-> N/A)
  lts/carbon -> v8.16.0 (-> N/A)
  lts/dubnium -> v10.15.3 (-> N/A)
  

• How did you install nvm? (e.g. install script in readme, Homebrew):
  Initially, using the provided curl script. Then I update a couple years later with the same curl command.

• What steps did you perform?
  I did an apt update followed by an apt upgrade and then rebooted. Then I tried to run nvm use node

• What happened?

node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by node)
node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by node)
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v12.2.0` to unset it.

• What did you expect to happen?
  I would be able to use node and npm.

• Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?
  No.

• If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?
  
  
  

```sh

```

[ljharb]

I assume that node wouldn’t work even if you installed it directly from the official installer - this implies that you need to install some additional things on your system before node or nvm can work.

[VictorioBerra]

Well it worked just fine before i went and did and update and upgrade and
then update the nvm script. Every article and thing i read says install
libgcc or libc++ but all of that is install already.

On Thu, May 9, 2019 at 2:41 PM Jordan Harband [e-mail]
wrote:

I assume that node wouldn’t work even if you installed it directly from
the official installer - this implies that you need to install some
additional things on your system before node or nvm can work.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/2044#issuecomment-491038664, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWMN2YEXYFGXXFVZH5KCG3PUR47HANCNFSM4HL5KANA
.

--
Victorio Berra
[email protected]
636-328-7110

[VictorioBerra]

Its looking like im going to just have to rebuild the RaspberryPI. From what I understand NVM should work on Raspbian Jessie without any additional things.

[ljharb]

As far as I’m aware, it does.

[VictorioBerra]

Unfortunately I had to do a full reflash.

I downloaded raspbian lite, flashed.
Enabled SSH and wifi.
SSHed in, and did an apt upgrade
Then I ran the NVM script
did nvm install node and my problems were solved.

Not sure how my OS got in such a messed up state. I dont do anything on their but run node and occasionally update.

[ljharb]

Glad you got it figured out :-)

[VictorioBerra]

I wouldn't call it figured out but thanks lol

[ljharb]

well, working then :-) happy to reopen if it happens again and there’s something nvm can do about it.

[Gennttii]

I am having same problem, is there any fix , or the only fix is to install fresh OS ..!!

[VictorioBerra]

@Gennttii If you find a fix without a clean install, please let me know.

[Gennttii]

Upgraded raspbian os from jessie to stretch
https://www.datenreise.de/en/raspberry-pi-raspbian-update-update-jessie-to-stretch/

then uninstalled and installed npm and nodejs, it worked..

[reinier-lolkema]

I got the same problem after trying to update node to the latest version using this command:
$ wget -O - https://raw.githubusercontent.com/audstanley/NodeJs-Raspberry-Pi/master/Install-Node.sh | sudo bash;
node -v;

To fix it I followed these instructions https://stackoverflow.com/questions/48359107/unable-to-update-nodejs-and-npm-on-raspbian-raspberry-pi-3 and uninstalled nodejs and re-installed it.
$ sudo apt-get remove nodejs nodejs-legacy -y
$ sudo apt-get install nodejs -y

[ljharb]

Installing node from apt isn’t really fixing it, unless you’re saying you were able to use nvm after that?

[reinier-lolkema]

No, I'm not using nvm. Forgive me if I have commented in the wrong context. I was trying to use node on a Pi running Jessie but thought the version reported by node -v was quite old, so I thought I'd better upgrade it using the Install-Node.sh script.
This broke node and it came up with exactly the same error from this issue. I found this post, but did not want to re-install the operating system, so kept looking for an easier solution to get node working again.
When I found it, I thought to add to this issue hoping it may help someone else in the future.

[VictorioBerra]

I recommend you do not install node from apt and instead use NVM.

On Thu, Jun 11, 2020, 5:49 PM Reinier Lolkema [e-mail]
wrote:

No, I'm not using nvm. Forgive me if I have commented in the wrong
context. I was trying to use node on a Pi running Jessie but thought the
version reported by node -v was quite old, so I thought I'd better upgrade
it using the Install-Node.sh script.
This broke node and it came up with exactly the same error from this
issue. I found this post, but did not want to re-install the operating
system, so kept looking for an easier solution to get node working again.
When I found it, I thought to add to this issue hoping it may help someone
else in the future.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/2044#issuecomment-642969307, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWMN2ZWTZMTYWLKYFIVTEDRWFNOXANCNFSM4HL5KANA
.