Jira (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono

[Michael Smith (JIRA)]

Title: Message Title

Michael Smith updated an issue   Facter / FACT-951 Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Change By: Michael Smith Boost.Log has an implicit dependency on Boost.Chrono. This results in Boost.Chrono being built on all platforms, and if Facter statically links in Boost or has Boost on the LD_LIBRARY_PATH, all dependencies are resolved. Neither was the case on Solaris, which exposed the implicit dependency on Boost.Chrono - when we explicitly link dynamic libraries, libfacter hard-codes their location, but since libboost_chrono wasn't explicitly linked it couldn't resolve its location. To avoid these kinds of issues, add an explicit dependency on chrono so the static path is setup correctly. Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.