LightGBM: lightGBM 2.2.200 still has glibc issue /lib64/libstdc++.so.6: version : GLIBCXX_3.4.20' not found
Thank you @xiaoxiaofengzi for the clarification! Unfortunately this is a known problem caused by that MMLSpark uses old and broken (in terms of dependencies) version of LightGBM.
You can track this PR and these issues 1, 2 to know when the problem will be solved on the Spark-package side. I think that you can copy-paste your log there to hurry them gently.
From the our side starting from 2.2.2 version we automatically guarantee GLIBC <= 2.14 and GLIBCXX <= 3.4.19:
https://github.com/Microsoft/LightGBM/blob/a694712b7fb86cd532eea2c1781b58d4ba58436a/helpers/check_dynamic_dependencies.py#L18-L23 https://github.com/Microsoft/LightGBM/blob/a694712b7fb86cd532eea2c1781b58d4ba58436a/helpers/check_dynamic_dependencies.py#L25-L31
Thanks for your patience and sorry for the inconvenience!
_Originally posted by @StrikerRUS in https://github.com/Microsoft/LightGBM/issues/1858#issuecomment-440610638_
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 29 (6 by maintainers)
@imatiach-msft Thanks for your review! As I said in my comment here https://github.com/Microsoft/LightGBM/pull/2125#issuecomment-485310784, artifacts are not published for PRs. They are published for each commit in any branch, but not for PRs. As I worked in
dockerbranch for that PR, you can find jar artifact in builds for this branch. https://github.com/Microsoft/LightGBM/blob/d115769c2a2ddffadc76c7b84739a47937114c77/.vsts-ci.yml#L56-L61https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=1856
@StrikerRUS sure, i think it is okay.
@guolinke Can you please answer to the question in last paragraph https://github.com/Microsoft/LightGBM/issues/1945#issuecomment-482305298? Your answer may make all further work pointless.
For normal usage, OpenJDK is fully compatible with Oracle JDK, so yes, there should be no issue with it.
EDIT: I recommend using OpenJDK 8 for widest compatibility.