The latest cli (1.32.0-245) cause "ERROR SHARED stderr {"data": "Error: /lib64/libstdc++.so.64: version `GLIBCXX_3.4.21` not found"....
See original GitHub issueDescription
Hi, the above problem raised when “Starting shared process[x/5]”, after I update my code-server cli from 1.31.1-100 to 1.32.0-245. It works properly when using the former version. I am wondering whether the latest cli depends on different C++ library from the former one?
PS: The message is: INFO Starting shared process [1/5]… ERROR SHARED stderr {“data”:"Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21’ not found (required by /path/to/my/home/.local/share/code-server/dependencies/spdlog.node)\n…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:19
- Comments:45 (3 by maintainers)
Top Results From Across the Web
"Error: /lib64/libstdc++.so.64: version `GLIBCXX_3.4.21` not ...
The latest cli (1.32.0-245) cause "ERROR SHARED stderr {"data": "Error: /lib64/libstdc++.so.64: version GLIBCXX_3.4.21 not found".... #239.
Read more >linux - GLIBCX_3.4.21 not found - Stack Overflow
After updating and installing all the basic things to run the project, I actually encountered the exact same error again.
Read more >com.ibm.cognos.tm1.TM1Exception: Could not load C API due ...
The error is caused by the missing libraries on your host. The PMPSVC Application Server requires additional libraries to be installed. The ...
Read more >lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
Hello. I'm trying to build and and install plv8 extension for Postgres 13 RHEL-7, but getting below error: Raw.
Read more >apt: relocation error: version GLIBCXX_3.4.21 not defined in ...
I had the same problem caused by issues from PPA for Ubuntu toolchain. My computer would not boot because of it.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Working on a fix for this right now. If all goes well, we’ll have a working CentOS build today!
Cry? /s
not sure… I’ll poke around again… I know I had this exact issue but I ended up fixing it at some point…
$ npm --version 6.9.0 $ node --version v8.15.0 $ yarn --version 1.13.0
maybe npm update?
npm install -g npm