Subject: [boost] Fw: Mysterious Boost.System-related errors when running Beast tests
From: Peter Dimov (lists_at_[hidden])
Date: 2018-05-05 12:10:23
The story starts with
which gives the error
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
but even if it didn't, it also links to Filesystem, which _is_ being built,
and Filesystem also depends on System in its build/Jamfile:
So Boost.System should be built, but it isn't. Its Jamfile hasn't been
touched in 10 years:
In addition, there's not even a `mklink-or-dir boost/system` in the log,
even though the link must be created because the new headers are being used
(this could be a separate issue).
The Linux/g++ job, https://travis-ci.org/vinniefalco/beast/jobs/375049187,
also doesn't seem to build Boost.System, but it works for some reason.
When I try `b2 libs/beast/test` on Windows, with msvc-14.1, Boost.System is
being built, in the very beginning:
...found 6992 targets...
...updating 1090 targets...
Hardlink created for ..\..\boost\utility\string_view.hpp <<===>>
(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?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk