Cryptic Boost.Build error (help required!)
Can anyone see what's wrong here: https://github.com/boostorg/regex/issues/89 ? The reduced test case is: |./b2 -sICU_PATH="/opt/some/path" -sICU_LINK="-L/opt/some/path/lib/x86_64-linux-gnu -licuuc -licudata -licui18n" toolset=gcc-8 -n --with-filesystem --with-log Many thanks, John. | -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
AMDG On 10/8/19 6:47 AM, John Maddock via Boost wrote:
Can anyone see what's wrong here: https://github.com/boostorg/regex/issues/89 ?
The reduced test case is:
|./b2 -sICU_PATH="/opt/some/path" -sICU_LINK="-L/opt/some/path/lib/x86_64-linux-gnu -licuuc -licudata -licui18n" toolset=gcc-8 -n --with-filesystem --with-log Many thanks, John. |
Short answer: the culprit is <install-dependencies>on in tools/boost_install/boost-install.jam Longer Answer: The stage targets for boost_log pick up the icu options as usage requirements from boost_regex. <install-dependencies>on, means that they will also copy filesystem, date_time, etc. These stage targets all have icu options applied, and Boost.Build isn't able to prove that the options are not important. These targets conflict with the targets generated by the stage target from boost_filesystem. commit 5bc0961483e5b95b72032e2c3439a7a9be7134f2 (tag: boost-1.70.0.beta1, origin/feature/stage-dependencies) Author: Peter Dimov Date: Sun Mar 10 02:46:01 2019 +0200 Use <install-dependencies>on when staging because of zlib/bzip2/zstd/lzma In Christ, Steven Watanabe
participants (2)
-
John Maddock
-
Steven Watanabe