-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnsatisfiedLinkError: libopensearchknn_faiss_avx512_spr.so: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found #2484
UnsatisfiedLinkError: libopensearchknn_faiss_avx512_spr.so: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found #2484
Comments
@peterzhuamazon can you pls take a look into this issue. Thanks! |
AL2023, which is our release image base, have AL2, which is our build image base, initially have However, since opensearch-project/opensearch-build#5226 AL2 for X64 has upgraded gcc from 10 to 12, which subsequently upgrade libstdc++.so to |
One solution is to also upgrade the gcc version on AL2023 so that the libgcc version is increased as well on x64. |
Hi @naveentatikonda could you provide a few API calls for me to test the change? Thanks. |
@peterzhuamazon here are some sample curl commands to test // Create Index
// Ingest docs
// Query index
|
Able to achieve the output here, will PR:
|
We are changing the strategy on this one. After building the gcc12 we will replace the newly released 6.0.30 back to 6.0.24 version of libstdgc++ to avoid using newer version for better backward compatibility due to bugs on barebone AL2 and AL2023 not compatible with 6.0.30.
Thanks. |
More errors, this time in nmslib:
|
The issue is related to nmslib do not support gcc11+, while faiss needs gcc12+ to build. cc: @naveentatikonda Then update build.gradle of k-NN repo to dynamically switch GCC with env vars. Thanks. |
Description
Running into UnsatisfiedLinkError during runtime while loading libopensearchknn_faiss_avx512_spr.so library when tested with 2.19 RC2 docker setup for k-NN (which is using GCC 12.4). But, no issues when tested with tar artifact.
The text was updated successfully, but these errors were encountered: