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
update the build of LightGBM python-package #87
Conversation
Hi there! I'm a little confused by this — is LightGBM not building correctly at the moment? |
@nerdcha We update the installation method, it doesn't need to build the cli version first. |
@guolinke Oh, I see! Thanks for correcting that, much appreciated! |
Hrm, this caused a build failure, and installing via |
@nerdcha It is very strange. Can you provide the error log ? |
Whoops: on rechecking the logs, it seems it wasn't the change itself, but the fact that LightGBM needs cmake 3.2+ now. I'm looking in to upgrading cmake from the |
okay, i see.
this should be the same as
But the latter is faster . |
Uh oh, looks like we're in DLL Hell: a
@guolinke Have you come across this issue before by any chance? |
@nerdcha it seems is the version of gcc is too low, or it has multi versions of gcc. |
@nerdcha BTW, I just relax the version of cmake in LightGBM master branch. So you don't need to install the cmake now. |
The weird thing is that the library file it claims to be looking in does have the symbol that it's searching for:
And the default version of gcc supports gomp 4
I resolved a similar issue some time in the past with a cheeky monkey patch, so I guess it's not the most stable solution. Maybe I'll try uninstalling Conda's gcc completely before adding gcc 4.9… |
No description provided.