Re: [Boost-users] bjam buil "hangs"

Subject: Re: [Boost-users] bjam buil "hangs"
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-04-06 10:00:32

Jean-Pierre Bergamin wrote:

> Hello everyone
> 
> I'm trying to build boost 1.42 on XP with Visual Studio 2005 with the
> following commands in the Visual Studio Command Prompt:
> 
>> set boost_dir=C:\Programme\boost\boost_1_42_0
>> bjam --build-type=complete --with-thread --with-test --with-system
> --with-serialization --with-regex --with-program_options --with-filesystem
> --with-date_time --prefix=%boost_dir% --includedir=%boost_dir%
> --libdir=%boost_dir%\lib --exec-prefix=%boost_dir% install
> 
> Now bjam "hangs", using 50% CPU (one core fully utilized), after this
> output:

For how long does it stay this way? Just want to make sure this is hang,
and not an unexpectedly slow, but ultimately successful, execution.

> D:\Downloads\boost_1_42_0>bjam --build-type=complete --with-thread
> --with-test --with-system --with-serialization --with-regex
> --with-program_options --with-filesystem --with-date_time
> --prefix=%boost_dir% --includedir=%boost_dir% --libdir=%boost_dir%\lib
> --exec-prefix=%boost_dir%  install
> WARNING: No python installation configured and autoconfiguration
>          failed.  See http://www.boost.org/libs/python/doc/building.html
>          for configuration instructions or pass --without-python to
>          suppress this message and silently skip all Boost.Python targets
> warning: No toolsets are configured.
> warning: Configuring default toolset "msvc".
> 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
> warning: Building Boost.Regex with the optional Unicode/ICU support
> disabled.
> note: Please refer to the Boost.Regex documentation for more information
> note: this is a strictly optional feature.
> 
> 
> 
> Interestingly enough, just running "bjam --build-type=complete" without any
> other options, starts the build as expected.
> 
> Any hints how to debug this?

Yes. Build bjam with debug info by going to tools/jam/src and running

        ./build.bat --debug

New bjam will be in bin.ntx86.debug directory. Run again with that bjam. When
it runs for a while and definitely hanged, run Visual Studio, attach to bjam
and get a stracktrace -- and post it here.

Thanks,
Volodya