Re: [Boost-build] Building Boost on AIX with vacpp coredumps

From: Christopher Cambly (ccambly_at_[hidden])
Date: 2008-06-09 12:52:15

>
> I'm trying to build Boost v1.34.1 on my AIX 5.2 (RISC) box running
> VisualAge 5.  I've attemted to run a make after the standard ./
> configure (which tries to build it using the gcc toolset).  I also
> built the vacpp toolset using build.sh and specifying that toolset
> (./configure --with-toolset=vacpp).  When I do a make using either
> config, the result is the same:
>
> tarkin$ make install
> ./tools/jam/src/bin.aix/bjam  --user-config=user-config.jam --
> prefix=/home/bld_acct/boost/boost_v1.34.1.SDK/AIX.5.
> 2_RISC_vacpp50_LP32 --exec-prefix=/home/bld_acct/boost/boost_v1.34.
> 1.SDK/AIX.5.2_RISC_vacpp50_LP32 --libdir=/home/bld_acct/boost/
> boost_v1.34.1.SDK/AIX.5.2_RISC_vacpp50_LP32/lib --includedir=/home/
> bld_acct/boost/boost_v1.34.1.SDK/AIX.5.2_RISC_vacpp50_LP32/include
install
> Building Boost.Regex with the optional Unicode/ICU support disabled.
> Please refer to the Boost.Regex documentation for more information
> (don't panic: this is a strictly optional feature).
> /usr/bin/sh: 29268 Segmentation fault(coredump)
> Not all Boost libraries built properly.
> Can someone please assist?
>

Typically this error is a result of bjam running out of memory.  Allowing
bjam to access a larger data section often corrects this problem. You can
do this by issuing "export LDR_CNTRL=MAXDATA=0x80000000" in your shell
prior to running "make install".

The best fix would be to add -bmaxdata:0x80000000 or the gcc equivalent as
a link option when building bjam executable.

FWIW, I'm not sure how well VA5 will work with Boost 1.34.1

Chris Cambly
XL C++ Compiler Development