The linker warnings appear to have gone away when I removed "HIDE_SYMBOLS=1” from my build arguments.
This StackOverflow question addresses the first few CMake warnings and a fix might be as simple as just changing some version info. (Build configs are not my speciality…) https://stackoverflow.com/a/46048639 Kenny > On Sep 16, 2017, at 3:19 AM, Larry Gritz <[email protected]> wrote: > > Yes, I've been seeing those extra cmake warnings, ever since I (that is, > Homebrew) upgraded Boost to 1.65. > > I have not seen any of the link warnings that you describe. But that, too, > appears to be a problem on the boost side of things? I'm not sure what we can > do to resolve it from our end. > > > >> On Sep 15, 2017, at 12:44 PM, Kenny Carruthers <[email protected]> >> wrote: >> >> Having just returned to building and integrating OIIO into my app after a >> few weeks, I’m encountering some warnings and errors that I hadn’t seen >> earlier. These are probably more related to build environments than anything >> specific to OIIO, but I was wondering if anyone had any thoughts since it’s >> OIIO that I’m trying to build. It used to work fine, but it’s causing some >> problems. A few things have changed: >> >> * I’m now running Xcode 9 GM on macOS 10.12.6 >> * Boost is now 1.65.1 installed via Cakebrew (Homebrew) >> * Latest OIIO code from master branch. >> >> My OIIO make command: >> >> # make BUILDSTATIC=1 LINKSTATIC=1 HIDE_SYMBOLS=1 USE_LIBCPLUSPLUS=1 >> USE_LIBRAW=1 USE_JPEGTURBO=1 USE_CPP=14 USE_FFMPEG=0 >> >> Right off the top, I now get a bunch of warnings that say: >> >> "CMake Warning at >> /usr/local/Cellar/cmake/3.8.1/share/cmake/Modules/FindBoost.cmake:765 >> (message):" >> "Imported targets not available for Boost version 106501” >> >> During the build itself, I also get a ton of linker warnings like so: >> >> ld: warning: direct access in function 'boost::exception_ptr […SNIP…] from >> file '/usr/local/lib/libboost_thread-mt.a(thread.o)' means the weak symbol >> cannot be overridden at runtime. This was likely caused by different >> translation units being compiled with different visibility settings. >> >> There are several questions on StackOverflow related to the visibility >> issue, but it’s not entirely clear to me how to resolve that with the OIIO, >> Boost and all the other dependencies. >> >> https://stackoverflow.com/questions/15059360 >> >> In the past, I’ve just installed the various OIIO dependencies using >> Homebrew. Then I dowloaded the OIIO source and built it manually using the >> command above. I then took all the appropriate static libraries and copied >> them into my main Xcode project and it “just worked”… But something has >> changed in the last few weeks and I wonder if anyone has any ideas regarding >> the above warnings. >> >> Cheers, >> Kenny >> _______________________________________________ >> Oiio-dev mailing list >> [email protected] >> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > -- > Larry Gritz > [email protected] > > > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
