v5.2.1 and v5.1.8 index does not work on CentOS 7

[therealdano]

It looks like the development system has a higher libstdc++ than CentOS 7. When I try to run index, I get:

$ ./index setup
./index: /lib64/libstdc++.so.6: version 'GLIBCXX_3.4.20 not found (required by ./index)
./index: /lib64/libstdc++.so.6: version 'GLIBCXX_3.4.21' not found (required by ./index)
./index: /lib64/libstdc++.so.6: version 'CXXABI_1.3.9' not found (required by ./index)

I am running libstdc++-4.8.5-39.el7.x86_64, which only has GLIBCXX_3.4.19 and CXXABI_1.3.7. Would it be possible to continue to support that version combination for a while? CentOS 7 will still get full updates until Q4 of 2020.

[asamuzaK]

The binaries are built using a module called nexe.
Therefore, I do not know in detail how nexe creates their binaries for each OS.
If you need such support, please contact the developer of nexe.

As a workaround, install Node.js and get withExEditorHost from npm.
For details, refer to Host setup from npm

[asamuzaK]

Ref How To Install Nodejs on CentOS/RHEL 7/6 - TecAdmin

[therealdano]

Thanks, the nodejs and host setup from npm instructions both worked.

As for the libstdc++ issue, I suppose I can attempt to create a binary with nexe on a CentOS 7 system and see what happens. When you create the binaries, do you use a Debian or Ubuntu host?

[asamuzaK]

I create 32bit binaries (both Windows and Linux) on my local Windows PC.
Other 64bit binaries (Windows, Mac, Linux) are created automatically by travis.

Binaries are for the people who find it difficult to install Node.js.
You already have Node.js installed, so you don't need to use binary anymore.

For a note, it seems that this issue is caused by V8 engine which Node.js uses.
See Node.js 12 - V8 version roadmap · Issue #25082 · nodejs/node

[asamuzaK]

I'll close this.