ERROR: something wrong with flag 'folly_hazptr_use_executor' in file 'Hazptr.cpp'. One possibility: file 'Hazptr.cpp' is being linked both statically and dynamically into this executable. · Issue #2428 · facebook/folly · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: something wrong with flag 'folly_hazptr_use_executor' in file 'Hazptr.cpp'. One possibility: file 'Hazptr.cpp' is being linked both statically and dynamically into this executable.
#2428
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.
I installed folly version 2025.02.24.00 via vcpkg and attempted to link it statically into my library. However, I encountered the following runtime error:
ERROR: Something is wrong with the flag 'folly_hazptr_use_executor' in the file 'Hazptr.cpp'. One possibility is that 'Hazptr.cpp' is being linked both statically and dynamically into this executable.
Based on #1495, it seems the problem might be related to gflags. Unfortunately, I haven’t been able to successfully link folly statically to gflags.
Does anyone have any suggestions or solutions?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
I installed folly version 2025.02.24.00 via vcpkg and attempted to link it statically into my library. However, I encountered the following runtime error:
ERROR: Something is wrong with the flag 'folly_hazptr_use_executor' in the file 'Hazptr.cpp'. One possibility is that 'Hazptr.cpp' is being linked both statically and dynamically into this executable.
Based on #1495, it seems the problem might be related to gflags. Unfortunately, I haven’t been able to successfully link folly statically to gflags.
Does anyone have any suggestions or solutions?
Thanks in advance!
The text was updated successfully, but these errors were encountered: