Opened 7 years ago

Closed 7 years ago

#11376 closed Bugs (fixed)

custom bcp build failed due to feature "<segmented-stacks>"

Reported by: anonymous Owned by: John Maddock
Milestone: To Be Determined Component: bcp
Version: Boost 1.58.0 Severity: Regression
Keywords: Cc:

Description

I'm used to create a subset of boost through bcp, with the following command:

$ ./bin.v2/tools/bcp/gcc-4.8/release/link-static/bcp --namespace=myboost --namespace-alias chrono date_time regex system thread asio smart_ptr bind config build ../myboost/

and now I get the following output:

INFO: tracking source dependencies of library smart_ptr due to presence of "void sp_scalar_constructor_hook( void * px, std::size_t size, void * pn );" in file "boost/smart_ptr/detail/sp_counted_impl.hpp"
INFO: tracking source dependencies of library date_time due to presence of "  //! Wrapper class to represent months in gregorian based calendar
  class BOOST_DATE_TIME_DECL greg_month : public greg_month_rep {" in file "boost/date_time/gregorian/greg_month.hpp"
INFO: tracking source dependencies of library serialization due to presence of "class BOOST_SERIALIZATION_DECL(BOOST_PP_EMPTY()) extended_type_info :
    private boost::noncopyable
{" in file "boost/serialization/extended_type_info.hpp"
INFO: tracking source dependencies of library regex due to presence of "BOOST_REGEX_DECL void BOOST_REGEX_CALL reset_stack_guard_page();" in file "boost/regex/config.hpp"
CAUTION: don't know how to trace depenencies through macro: "BOOST_REGEX_H1" in file: boost/regex/pending/static_mutex.hpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_REGEX_H2" in file: boost/regex/pending/static_mutex.hpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_REGEX_H3" in file: boost/regex/pending/static_mutex.hpp
INFO: tracking source dependencies of library thread due to presence of "            class BOOST_THREAD_DECL scoped_winrt_thread
            {" in file "boost/thread/win32/thread_primitives.hpp"
CAUTION: don't know how to trace depenencies through macro: "BOOST_ATOMIC_DETAIL_HEADER(boost/atomic/detail/caps_)" in file: boost/atomic/capabilities.hpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_ATOMIC_DETAIL_HEADER(boost/atomic/detail/ops_)" in file: boost/atomic/detail/operations_lockfree.hpp
INFO: tracking source dependencies of library atomic due to presence of "struct lockpool
{" in file "boost/atomic/detail/lockpool.hpp"
INFO: tracking source dependencies of library exception due to presence of "        int clone_current_exception_non_intrusive( clone_base const * & cloned );" in file "boost/exception/detail/clone_current_exception.hpp"
INFO: tracking source dependencies of library program_options due to presence of "     *  concrete classes. */
    class BOOST_PROGRAM_OPTIONS_DECL invalid_syntax : public error_with_option_name {" in file "boost/program_options/errors.hpp"
CAUTION: don't know how to trace depenencies through macro: "BOOST_TYPE_INDEX_USER_TYPEINDEX" in file: boost/type_index.hpp
INFO: tracking source dependencies of library coroutine due to presence of "struct BOOST_COROUTINES_DECL stack_traits
{" in file "boost/coroutine/stack_traits.hpp"
INFO: tracking source dependencies of library filesystem due to presence of "  BOOST_FILESYSTEM_DECL const system::error_category& codecvt_error_category();" in file "boost/filesystem/path_traits.hpp"
CAUTION: dependent file libs/filesystem/v2 does not exist.
   Found while scanning file boost/filesystem.hpp
CAUTION: dependent file libs/filesystem/v3 does not exist.
   Found while scanning file boost/filesystem.hpp
CAUTION: dependent file Jamrules does not exist.
   Found while scanning file tools/build/boost-build.jam
CAUTION: dependent file project-root.jam does not exist.
   Found while scanning file tools/build/boost-build.jam
CAUTION: dependent file Jamfile.v2 does not exist.
   Found while scanning file tools/build/boost-build.jam
CAUTION: dependent file tools/build/test/../../../../boost.png does not exist.
   Found while scanning file tools/build/test/test_system.html
CAUTION: don't know how to trace depenencies through macro: " "gc_local_alloc.h"" in file: tools/build/src/engine/boehm_gc/include/gc.h
Copying file:...
no errors detected

then from myboost directory, building my subset

cd ../myboost
./bootstrap.sh
./b2

but with version 1.58 I get the following error:

myboost/tools/build/src/build/feature.jam:326: in validate-feature from module feature
error: unknown feature "<segmented-stacks>"
myboost/tools/build/src/build/feature.jam:360: in expand-subfeatures-aux from module feature
myboost/tools/build/src/build/feature.jam:425: in feature.expand-subfeatures from module feature
myboost/tools/build/src/build/property.jam:508: in property.translate from module property
myboost/tools/build/src/build/property-set.jam:432: in property-set.create-from-user-input from module property-set
myboost/tools/build/src/build/property-set.jam:484: in property-set.refine-from-user-input from module property-set
myboost/tools/build/src/build/project.jam:700: in class@project-attributes.set from module object(project-attributes)@287
myboost/tools/build/src/build/project.jam:1073: in project from module project-rules
libs/coroutine/build/Jamfile.v2:29: in modules.load from module Jamfile<myboost/libs/coroutine/build>
myboost/tools/build/src/build/project.jam:325: in load-jamfile from module project
myboost/tools/build/src/build/project.jam:64: in load from module project
myboost/tools/build/src/build/project.jam:89: in load-used-projects from module project
myboost/tools/build/src/build/project.jam:75: in load from module project
myboost/tools/build/src/build/project.jam:145: in project.find from module project
myboost/tools/build/src/build-system.jam:535: in load from module build-system
myboost/tools/build/src/kernel/modules.jam:289: in import from module modules
myboost/tools/build/src/kernel/bootstrap.jam:139: in boost-build from module
myboost/boost-build.jam:17: in module scope from module

seems like bcp isn't able to track down all dependencies

Change History (3)

comment:1 by anonymous, 7 years ago

Is there any update to this? I am also hitting a similar issue.

comment:2 by John Maddock, 7 years ago

A temporary workaround is to add "context" to the list of libraries to copy - bcp is unable to trace the dependencies through context's assembly files.

I'll try and get this fixed for the next release.

comment:3 by John Maddock, 7 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.