-
Notifications
You must be signed in to change notification settings - Fork 266
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
How to properly link the gflags? #22
Comments
configure glags as shared library which is not the default option! |
But it seems that the default configuration do treat gflags as shared library. Am i missing something ?🤔 I will try to reproduce this problem in a brand new environment later. |
Obviously. In fact, I have already noticed that and done a similar job in a build script here But i do not think this is the key point of the problem. What I concern is that do we need to compile gflags manually or not? After testing in a brand new environment and reading your notes, i can pretty sure that the answer is yes: we do need to build gflags manually. I will try to submit a PR to automate this process. Thanks for your communication! |
@CNLHC Great thanks for your PR. Would you mind show your building steps and commands that lead to the errors exactly? I did not reproduce the problem in my environment. |
The reproducing steps
then , got error
os
and kernel-version
|
Building the python wheel from
master
branch and run gcn model will getIt seems that symbol
_ZN6google14FlagRegistererC1IiEEPKcS3_S3_PT_S5_
(which is the mangledFlagRegisterer
from gflags package ) was not found.So, I tried to modify the
Makefile
and linkgflags
library manually, then the problem was solved.(modified line: here)Is this a bug or one need special way not mentioned in doc so far to link gflags ?
The text was updated successfully, but these errors were encountered: