Hello all, I'm trying to build boost 1.33 64-bit libraries under HP-UX 11.23 with the help of gcc 4.1.1 thru bjam. I was confused trying to supply -mlp64 compiler and linker option to the gcc though bjam options. By default calling ``bjam'' uses Boost.Build v.1, and setting ``bjam --v2'' -- will do v.2. Uncommenting "using gcc ;" in ./tools/build/v2/ user-config.jam file led bjam to "learn" this toolset, but calling ``bjam --v2'' from the boost_1_33_0/ folder splashes this: # bjam --v2 gcc warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). /home/avinokur/boost_1_33_0/tools/build/v2/build/virtual-target.jam:868: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage>libboost_date_time-gcc-d-1_33.so.1.33.0 error: previous virtual target { common%common.copy-libboost_date_time-gcc-d-1_33.so.1.33.0.SHARED_LIB { gcc%gcc.link.dll-libboost_date_time-gcc-d-1_33.so.1.33.0.SHARED_LIB { gcc%gcc.compile.c++-greg_month.o.OBJ { gregorian/greg_month.cpp.CPP } } { gcc%gcc.compile.c++-greg_weekday.o.OBJ { gregorian/greg_weekday.cpp.CPP } } { gcc%gcc.compile.c++-date_generators.o.OBJ { gregorian/date_generators.cpp.CPP } } } } error: created from ./stage error: another virtual target { common%common.copy-libboost_date_time-gcc-d-1_33.so.1.33.0.SHARED_LIB { common%common.copy-libboost_date_time-gcc-d-1_33.so.1.33.0.SHARED_LIB { gcc%gcc.link.dll-libboost_date_time-gcc-d-1_33.so.1.33.0.SHARED_LIB { gcc%gcc.compile.c++-greg_month.o.OBJ { gregorian/greg_month.cpp.CPP } } { gcc%gcc.compile.c++-greg_weekday.o.OBJ { gregorian/greg_weekday.cpp.CPP } } { gcc%gcc.compile.c++-date_generators.o.OBJ { gregorian/date_generators.cpp.CPP } } } } } error: created from ./stage error: added properties: none error: removed properties: none /home/avinokur/boost_1_33_0/tools/build/v2/build/virtual-target.jam:175: in actualize-no-scanner from module object(file-target)@269 /home/avinokur/boost_1_33_0/tools/build/v2/build/virtual-target.jam:110: in object(file-target)@269.actualize from module object(file-target)@269 /home/avinokur/boost_1_33_0/tools/build/v2/build-system.jam:285: in load from module build-system /home/avinokur/boost_1_33_0/tools/build/v2/kernel/modules.jam:259: in import from module modules /home/avinokur/boost_1_33_0/tools/build/v2/kernel/bootstrap.jam:153: in boost-build from module /home/avinokur/boost_1_33_0/boost-build.jam:12: in module scope from module Calling v.1 Boost.Built with "cxxflags=-mlp64" got no luck too: # bjam cxxflags=-mlp64 --------------------------------------------------------------------- *** If you don't need Boost.Python, you can ignore this section *** *** pass --without-python to suppress this message in the future *** skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/usr/local/include/python2.2" You can configure the location of your python installation by setting: PYTHON_ROOT - currently "/usr/local" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "/usr/local/lib/python2.2/config" PYTHON_INCLUDES - path to Python #include directories; currently "/usr/local/include/python2.2" --------------------------------------------------------------------- Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). don't know how to make cxxflags=-mlp64 ...found 1 target... ...can't find 1 target... Finally the only way to get this 64-bit libs was this hack: ``GXX="g++ -mlp64" bjam''. Does anybody knows what the heck is with the bjam --v2 and why it is unable to build boost from-the-box? Aleksandr. PS. This is my gcc version, but seems it is not clued anyway: # gcc -v Using built-in specs. Target: ia64-hp-hpux11.23 Configured with: ../gcc/configure Thread model: posix gcc version 4.1.1