You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this error cased NATIVE be NULL, so the voicePlayer didnt work:
Error: node-loader:
Error: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /.vscode/extensions/kaiyi.qwerty-learner-0.3.7/dist/0499bc3cb3e2b70114d4091e8eb506dd.node)
may be its because the linux-x64.node so is compiled on Ubuntu which has newer version of glibc lib.
my Centos only support to GLIBC_2.28, maybe such nativemod should be based on lower version of glibc to support more linux release version? or maybe we can add a new .node binary so to satisfied support from users like me.
by the way one can check if the same err occur to you by doing this:
ldd [your home path mostly]/.vscode/extensions/kaiyi.qwerty-learner-0.3.7/dist/0499bc3cb3e2b70114d4091e8eb506dd.node
you will find error like i quote above if you have the same problem.
The text was updated successfully, but these errors were encountered:
This error caused by GLIBC dynamic linking library is hardly to be tackled unless Neon which is used for embedding Rust would support compiling static modules such as using MUSL, but it seems not yet supported as this issue mentioned: neon-bindings/neon#823 (comment)
this error cased NATIVE be NULL, so the voicePlayer didnt work:
may be its because the linux-x64.node so is compiled on Ubuntu which has newer version of glibc lib.
my Centos only support to GLIBC_2.28, maybe such nativemod should be based on lower version of glibc to support more linux release version? or maybe we can add a new .node binary so to satisfied support from users like me.
by the way one can check if the same err occur to you by doing this:
ldd [your home path mostly]/.vscode/extensions/kaiyi.qwerty-learner-0.3.7/dist/0499bc3cb3e2b70114d4091e8eb506dd.node
you will find error like i quote above if you have the same problem.
The text was updated successfully, but these errors were encountered: