dyld: Symbol not found: __ZN5boost6system6detail19system_category_ncxEv
Expected in: /usr/local/lib/libboost_system.dylib
boost::system::detail::system_category_ncx is a new function (in develop),
and careful reading of the above reveals that the compiler is trying to link
to a preinstalled libboost_system.dylib, in /usr/local/lib.
Looking at the log, Boost.System is not even being built. This is odd; the
Beast root Jamfile contains
(The 1.66 version instead of 1.68 was caused by a typo in the superproject
which is now fixed.)
When I try the same on Ubuntu Trusty, the result is the same as on Travis;
no `mklink-or-dir boost/system`, no building of Boost.System, yet everything
compiles and works, and I don't have a preinstalled Boost on my VM.
It makes no sense at all.
Does anyone have any ideas what might be happening here?
Re: Fw: Mysterious Boost.System-related errors when running Beast tests
> When I try the same on Ubuntu Trusty, the result is the same as on Travis;
> no `mklink-or-dir boost/system`, no building of Boost.System, yet
> everything compiles and works, and I don't have a preinstalled Boost on my
> It makes no sense at all.
Examining the boost/ and bin.v2/ directories however reveals that
Boost.System has been symlinked and built.
It almost looks like all lines containing 'system' are hidden from the b2
output, but cursory examination shows no such logic there.