[Boost-build] bjam command hangs

Subject: [Boost-build] bjam command hangs
From: Michael Alexeev (michael.alexeev_at_[hidden])
Date: 2009-12-13 21:44:32

Hi All,

I am trying to install several boost libraries from the 1.40.0 release
on SuSe Linux 10.1 but having problem with the bjam command

shell> ./bootstrap.sh
--with-libraries=thread,serialization,filesystem,program_options,test
--with-toolset=gcc
Building Boost.Jam with toolset gcc... tools/jam/src/bin.linuxx86_64/bjam
Unicode/ICU support for Boost.Regex?... not found.
Generating Boost.Build configuration in project-config.jam...

Bootstrapping is done. To build, run:

    ./bjam

To adjust configuration, edit 'project-config.jam'.
Further information:

   - Command line help:
     ./bjam --help

   - Getting started guide:
     http://www.boost.org/more/getting_started/unix-variants.html

   - Boost.Build documentation:
     http://www.boost.org/boost-build2/doc/html/index.html

shell> ./bjam --help
Boost.Build V2 (Milestone 12)
Boost.Jam 03.1.17

Project-specific help:

  Project has jamfile at Jamroot

Usage:

  bjam [options] [properties] [install|stage]

  Builds and installs Boost.

Targets and Related Options:

  install                 Install headers and compiled library files to the
  =======                 configured locations (below).

  --prefix=<PREFIX>       Install architecture independent files here.
                          Default; C:\Boost on Win32
                          Default; /usr/local on Unix. Linux, etc.

  --exec-prefix=<EPREFIX> Install architecture dependent files here.
                          Default; <PREFIX>

  --libdir=<DIR>          Install library files here.
                          Default; <EPREFIX>/lib

  --includedir=<HDRDIR>   Install header files here.
                          Default; <PREFIX>/include

  stage                   Build and install only compiled library files
  =====                   to the stage directory.

  --stagedir=<STAGEDIR>   Install library files here
                          Default; ./stage

Other Options:

  --build-type=<type>     Build the specified pre-defined set of variations
                          of the libraries. Note, that which variants get
                          built depends on what each library supports.

                              minimal (default) - Builds a minimal set of
                              variants. On Windows, these are static
                              multithreaded libraries in debug and release
                              modes, using shared runtime. On Linux, these
                              are static and shared multithreaded libraries
                              in release mode.

                              complete - Build all possible variations.

  --build-dir=DIR         Build in this location instead of building
                          within the distribution tree. Recommended!

  --show-libraries        Displays the list of Boost libraries that require
                          build and installation steps, then exit.

  --layout=<layout>       Determines whether to choose library names
                          and header locations such that multiple
                          versions of Boost or multiple compilers can
                          be used on the same system.

                              versioned (default) - Names of boost binaries
                              include the Boost version number, name and
                              version of the compiler and encoded build
                              properties.  Boost headers are installed in a
                              subdirectory of <HDRDIR> whose name contains
                              the Boost version number.

                              tagged -- Names of boost binaries include the
                              encoded build properties such as variant and
                              threading, but do not including compiler name
                              and version, or Boost version. This option is
                              useful if you build several variants of Boost,
                              using the same compiler.

                              system - Binaries names do not include the
                              Boost version number or the name and version
                              number of the compiler.  Boost headers are
                              installed directly into <HDRDIR>.  This option
                              is intended for system integrators who are
                              building distribution packages.

  --buildid=ID            Adds the specified ID to the name of built
                          libraries.  The default is to not add anything.

  --help                  This message.

  --with-<library>        Build and install the specified <library>
                          If this option is used, only libraries
                          specified using this option will be built.

  --without-<library>     Do not build, stage, or install the specified
                          <library>. By default, all libraries are built.

Properties:

  toolset=toolset         Indicates the toolset to build with.

  variant=debug|release   Select the build variant

  link=static|shared      Whether to build static or shared libraries

  threading=single|multi  Whether to build single or multithreaded binaries

  runtime-link=static|shared
                          Whether to link to static or shared C and C++ runtime.

The problem is that bjam never returns. I have to kill the process
manually. Also any other bjam command does not produce any output at
all and  simply hangs.

Does anybody else experience similar problem? Any help is greatly appreciated.

Thanks,
Mike