Skip to content
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

Fix Boost warnings on macOS build #15

Closed
apkar opened this issue Nov 30, 2018 · 3 comments · Fixed by #206
Closed

Fix Boost warnings on macOS build #15

apkar opened this issue Nov 30, 2018 · 3 comments · Fixed by #206
Assignees
Labels
good first issue Good for newcomers

Comments

@apkar
Copy link
Contributor

apkar commented Nov 30, 2018

Linking        bin/fdbdoc
ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.
ld: warning: text-based stub file /System/Library/Frameworks//IOKit.framework/IOKit.tbd and library file /System/Library/Frameworks//IOKit.framework/IOKit are out of sync. Falling back to library file for linking.
ld: warning: direct access in function 'boost::system::error_category::std_category::equivalent(int, std::__1::error_condition const&) const' from file '.objs/./ConsoleMetric.actor.g.cpp.o' to global weak symbol 'typeinfo for boost::system::error_category::std_category' from file '/Users/bmuppana/src/boost_1_67_0/stage/lib/libboost_filesystem.a(codecvt_error_category.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
ld: warning: direct access in function 'boost::system::error_category::std_category::equivalent(std::__1::error_code const&, int) const' from file '.objs/./ConsoleMetric.actor.g.cpp.o' to global weak symbol 'typeinfo for boost::system::error_category::std_category' from file '/Users/bmuppana/src/boost_1_67_0/stage/lib/libboost_filesystem.a(codecvt_error_category.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
ld: warning: direct access in function 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >::rethrow() const' from file '.extdep/osx/flow-6.0.8-osx-x86_64/lib/libflow.a(Net2.actor.g.cpp.o)' to global weak symbol 'typeinfo for boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >' from file '.objs/./IMetric.cpp.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
@apkar apkar added the good first issue Good for newcomers label Nov 30, 2018
@dongxinEric
Copy link
Contributor

This could possibly be resolved if we can make sure to use the same visibility flags when compiling the boost binaries.

Sent with GitHawk

@senthil-db-expert
Copy link

@apkar we could fix this issue, please assign to me.
Approach,
Linking the recent frameworks from MacOSX.sdk to “/Library/Frameworks/”. Linking the proper library while do make (library flags should be visible through out the make process)

@senthil-db-expert
Copy link

senthil-db-expert commented Aug 16, 2019

@apkar For the Boost warnings, we have updated the parameters in README.md file to fix them. But for fixing the Framework warnings, it require manual steps. Can we just add those instructions to same README.md file?

drkannan added a commit to drkannan/fdb-document-layer that referenced this issue Aug 20, 2019
apkar added a commit that referenced this issue Aug 21, 2019
Resolves #15: Solution for Boost library and Framework related warnings on Mac OS build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
3 participants