Last commit has broken the instalation on CentOS7
keklabs opened this issue · 6 comments
In my opinion this commit a526db6
has rewriten the published binary
https://hummus.s3-us-west-2.amazonaws.com/hummus/v1.0.110/node-v83-linux-x64-glibc.tar.gz
becase we have one container with hummus instaled more than 10 days ago and this container has
[root@d447d3a54e2d binding]# strings hummus.node | grep GLIBCXX
GLIBCXX_3.4.6
GLIBCXX_3.4.9
GLIBCXX_3.4.15
GLIBCXX_3.4
and is working on CentOS7 where the last version is GLIBCXX_3.4.19
but current version requires
[root@c35e0b799ece binding]# strings hummus.node | grep GLIBCXX
GLIBCXX_3.4.20
GLIBCXX_3.4.9
GLIBCXX_3.4.21
GLIBCXX_3.4.15
GLIBCXX_3.4
and throws
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /var/appserver/node_modules/hummus/binding/hummus.node)
from my point of view, the binary should not be republished but there shuld be published new version like /v1.0.111
with this commit, to have possibility to fix the dependency on specific version.
Thank you
same as me, I have the same issue too
I got this error when I have built nodejs in docker:
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /var/appserver/node_modules/hummus/binding/hummus.node)
please help to fix this in version v.1.0.110
same as me, now my solution is to use a lower hummus version 1.0.108 ：(
@galkahana Is there any "official" communication regarding this "change". I thought this project is not supported anymore, so what's going on here? Breaking already released versions by exchanging some libs in the background is not the best way I think.
please consider change to https://github.com/julianhille/MuhammaraJS it is actively maintained
@julianhille I just tried out MuhammeraJS, and it has the same problem.
@julianhille and I worked on this issue over on the MuhammaraJS project. Julian came up with a workaround, so if you're still dealing with this issue, you might want to go take a look at that thread: julianhille/MuhammaraJS#158