@anmonteiro do you know anything about this error?
/codebuild/output/tmp/versions/node/v9.11.1/lib/node_modules/lumo-cljs/bin/lumo: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /codebuild/output/tmp/versions/node/v9.11.1/lib/node_modules/lumo-cljs/bin/lumo)
is lumo missing a dependency? or do I need to install that version of GLIBC via some other means?
hrm
@johanatan which dist/ version of linux does that machine run
aws/codebuild/java:openjdk-9
I'll try to find out what that isi think Ubuntu 13
yeah… that sounds right
actually 14.04
Defined here: https://github.com/aws/aws-codebuild-docker-images/tree/master/ubuntu/java/openjdk-9
can you upgrade to a later version of ubuntu?
14.04 is pretty late yea?
or just install libstdc++6
well…
14.04 means April 2014
ooh, right
how to install libstdc++6 ? via apt-get?
I thought it wasn't possible to install linux in the first place without libstdc++.so.6
this looks like it: https://askubuntu.com/questions/726539/sudo-apt-get-install-libstdc?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
@johanatan yes, apt-get install -y libstdc++6
what's your output johnatan when you do echo $LD_LIBRARY_PATH
@hlolli just a sec. not a live environment so i have to wait for runs to complete. trying that SO suggestion first
readelf -d lumo ~/.npm-global/lib/node_modules/lumo-cljs/bin
Dynamic section at offset 0x3914dc0 contains 30 entries:
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libdl.so.2]
0x0000000000000001 (NEEDED) Shared library: [librt.so.1]
0x0000000000000001 (NEEDED) Shared library: [libstdc++.so.6]
0x0000000000000001 (NEEDED) Shared library: [libm.so.6]
0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
looks pretty dynamically linked. So I wonder why your linker searched in /usr/lib/x86_64-linux-gnu
... curious to know and learn 🙂same elf signature in node for me, so I wonder if node runs for you.
yea, node runs fine
there's some difference there actually between node 9.8.0 and latest lumo on npm
readelf -sW lumo | grep GLIBCXX_3.4.20 ~/.npm-global/lib/node_modules/lumo-cljs/bin
7: 0000000000000000 0 FUNC GLOBAL DEFAULT UND _ZSt24__throw_out_of_range_fmtPKcz@GLIBCXX_3.4.20 (5)
17298: 0000000000000000 0 FUNC GLOBAL DEFAULT UND _ZSt24__throw_out_of_range_fmtPKcz@@GLIBCXX_3.4.20
readelf -sW ./node | grep GLIBCXX_3.4.20 ~/.nvm/versions/node/v9.8.0/bin
$
could be totally unrelated, was struggling recently to patchelf the lumo binary for nixos, I believe it's a stripped binary. I say with grain of salt only after some hours of research on complex topic.could be that your libstc++ version is just old
GCC 4.9.0: GLIBCXX_3.4.20, CXXABI_1.3.8
release date:
2014-04-22 07:11
maybe we can rethink about statically linking lumo. I wasn't able to load dynamically linked native node modules on runtime with statically linked lumo, it just crashed. Maybe since then it has been fixed, or we can find a workaround on that.
Any plans for packaging lumo-cljs for raspberry pi via npm in the future?