--build-type=complete broken in current svn

[Neal Becker <ndbecker2@…>]

bjam -sICU_PATH=/usr -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 --layout=system --build-type=complete stage warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Building Boost.Regex with Unicode/ICU support enabled Using ICU in /usr/include warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "--toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: ​http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html Skipping build of: ./stage <build>no in common properties Skipping build of: ./stage <build>no in common properties Skipping build of: ./stage <build>no in common properties Skipping build of: ./stage <build>no in common properties Skipping build of: libs/regex/build/icucore <build>no in common properties Skipping build of: libs/regex/build/icuin <build>no in common properties Skipping build of: libs/regex/build/icudata <build>no in common properties /usr/local/src/boost.hg/tools/build/v2/kernel/class.jam:93: in new * argument error

• rule object(searched-lib-target)@8387.init ( name : project : shared ? : search * : action )
• called with: ( icudata icui18n icuuc : object(project-target)@197 : true : : object(null-action)@8386 : : : : )
• extra argument icui18n

/usr/local/src/boost.hg/tools/build/v2/tools/builtin.jam:355:see definition of rule 'init' being called /usr/local/src/boost.hg/tools/build/v2/tools/builtin.jam:598: in searched-lib-generator.run /usr/local/src/boost.hg/tools/build/v2/tools/unix.jam:113: in object(unix-searched-lib-generator)@345.run /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:859: in try-one-generator-really /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:920: in try-one-generator /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:1131: in construct-really /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:1204: in generators.construct /usr/local/src/boost.hg/tools/build/v2/tools/builtin.jam:502: in object(lib-generator)@5.run /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:859: in try-one-generator-really /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:920: in try-one-generator /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:1131: in construct-really /usr/local/src/boost.hg/tools/build/v2/build/generators.jam:1204: in generators.construct /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1368: in construct /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1206: in object(typed-target)@209.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:742: in generate-really /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:715: in object(main-target)@861.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:254: in object(project-target)@197.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1129: in generate-dependencies /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1179: in object(install-target-class)@81.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:742: in generate-really /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:715: in object(main-target)@380.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1129: in generate-dependencies /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:1179: in object(alias-target-class)@85.generate /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:742: in generate-really /usr/local/src/boost.hg/tools/build/v2/build/targets.jam:715: in object(main-target)@384.generate /usr/local/src/boost.hg/tools/build/v2/build-system.jam:663: in load /usr/local/src/boost.hg/tools/build/v2/kernel/modules.jam:267: in import /usr/local/src/boost.hg/tools/build/v2/kernel/bootstrap.jam:132: in boost-build /usr/local/src/boost.hg/boost-build.jam:11: in module scope

[Vladimir Prus]

Do you mean this issue happens only with --build-type=complete?

[Neal Becker <ndbecker2@…>]

I can't say 'only' since I have only tested 3 cases:

1) Don't specify anything, I get MT 2) specify threading=single -> OK 3) --build-type=complete -> error

[anonymous]

remove the -sICU_PATH and it will probably work... EXPAT_LIBPATH and _INCLUDE have to specified as env-variables, not as bjam variables as it seems...

[Vladimir Prus]

(In [45245]) Don't assign build properties as target's usage requirements when it fails to generate.

We try to avoid building the same target twice, by caching the result of previous calls to target.generate, and returning it if a build request with the same property set is made. When the target fails to generate, for example due to <build>no property, we used to store the entire build property set as the usage requirements of the build. This is clearly, wrong, this patch makes us store <build>no as usage requirements instead.

Fixes #1816.