(Can't test more recent versions of facter because of bug 565008 which cripples >=3.1.0, but probably affects those too) When boost is built without the "nls" use flag, facter will fail eventually with the following error: In file included from /var/tmp/portage/dev-ruby/facter-3.0.2-r1/work/all/facter-3.0.2/vendor/leatherman/vendor/boost-nowide/boost/nowide/fstream.hpp:13:0, from /var/tmp/portage/dev-ruby/facter-3.0.2-r1/work/all/facter-3.0.2/lib/src/facts/external/yaml_resolver.cc:8: /var/tmp/portage/dev-ruby/facter-3.0.2-r1/work/all/facter-3.0.2/vendor/leatherman/vendor/boost-nowide/boost/nowide/convert.hpp:12:41: fatal error: boost/locale/encoding_utf.hpp: No such file or directory #include <boost/locale/encoding_utf.hpp> Once boost is built with nls, facter builds fine. Is this an issue with facter in that it depends on natural language support when it shouldn't (thus upstream issue) or that NLS is a hard requirement and we just need to add an RDEP on boost and nls?
fixed in 3.1.2
