"Vladimir Prus" wrote in message news:...

Vinokurov, Aleksandr wrote:

...

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 {

....

...

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?

Probably an answer with a question is in order -- what's the heck with trying to build outdated version of Boost, in the first place? Second, Boost.Build V2 is officially used started with 1.34. Surely, even if had bug in 1.33, nobody's going to fix that.

- Volodya

Okay: 1. I have no free time (just now) to spend upgrading my current project from Boost 1.33 to latest one and finding/fixing misplaces and new bugs. 2. If Boost.Build v2 official release was in 1.34, why it was shipped with Boost 1.33 archive? And there are no documentation (looked on the site) on how to force compiler option when using v1 Boost.Build? Sincerely yours, Aleksandr

...

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