----- On 12 Oct, 2015, at 07:43, Ryan Schmidt ryandes...@macports.org wrote:
>> :info:build "libebml::EbmlString::SetValue(std::__1::basic_string<char, >> std::__1::char_traits<char>, std::__1::allocator<char> > const&)" >> "libebml::EbmlUnicodeString::SetValueUTF8(std::__1::basic_string<char, >> std::__1::char_traits<char>, std::__1::allocator<char> > const&)" >> :info:build "libebml::UTFstring::SetUTF8(std::__1::basic_string<char, >> std::__1::char_traits<char>, std::__1::allocator<char> > const&)" >> :info:build "libebml::EbmlString::operator std::__1::basic_string<char, >> std::__1::char_traits<char>, std::__1::allocator<char> > const &() const" Each of those missing symbols contains std::__1::basic_string, which makes me guess this is a problem with libstdc++ vs. libc++. If you actually check for the symbols in libebml.dylib and pass them through c++filt I bet there's std::string in there because libebml doesn't correctly compile against libc++. -- Clemens Lang _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
