b2 hangs with 'stage install'

[Antony Polukhin]

For a VERY long time nothing is printed after:

./b2 -j4 cxxflags="-std=c++0x" -d+2 --prefix=/home/cc/dev/boost_1_49_0_beta1 --build-type=complete --layout=tagged --with-date_time --with-thread --with-program_options --with-regex --with-test --with-system --with-serialization --with-graph --with-filesystem --disable-filesystem2 stage install

Performing configuration checks

    - has_icu builds           : yes

CPU load is 100%, but nothing is being compiled

If I remove install everything is OK

[anonymous]

The same here on Windows 7 x64 with Visual Studio 2008 x64. Hangs after some configuration checks on: b2 -j8 toolset=msvc --build-type=complete --libdir=.\lib\x64 architecture=x86 address-model=64 install

[awl03@…]

Likewise on Linux, cross-compiling for windows:

./bjam --user-config="${build_path}/mingw64-config.jam" --layout=versioned --toolset=gcc-mingw64 define=BOOST_USE_WINDOWS_H address-model=64 threadapi=win32 target-os=windows --with-filesystem --with-system --with-test --prefix="${build_path}/local_root" install

The mingw64-config.jam just contains: using gcc : mingw64 : x86_64-w64-mingw32-g++ ;

It sits using 100% CPU, giving no output, for about 10. Then suddenly it springs into life and completes the install.

I notice that, once it recovers, install says:

...patience... ...found 19901 targets...

whereas stage, which doesn't hang, says:

...patience... ...found 1139 targets...

I'm not sure what accounts for the difference.

[Steven Watanabe]

I can't replicate this. It's possible that bjam is exhausting physical memory. bjam uses a lot of memory, although it's much better than it used to be. If it starts hitting swap it will be quite slow.