Re: [Boost-build] bjam from 1.49.0 aborts on 100k targets project without message on AIX/gcc-4.6

Subject: Re: [Boost-build] bjam from 1.49.0 aborts on 100k targets project without message on AIX/gcc-4.6
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-03-15 15:03:51

AMDG

On 03/15/2012 11:50 AM, Frank Birbacher wrote:
> Hi,
> 
> I'm trying to build a software project that comprises of approx 250
> libraries. bjam actually builds parts of the libraries, but not all of
> them at once. It shall link an application that depends on all libs,
> but it aborts before compilation. I estimate some 100k targets found
> and some 2.5k targets to be built (using -a switch). But bjam will
> abort before showing the real numbers:
> 
> - "bjam" alone takes 40s, prints nothing, and aborts
> - "bjam --debug-building" takes 40s, prints lots of targets, and aborts
> - "bjam -n" takes 40s, prints some commands, then aborts; the command
> to link the final exe is missing
> - "bjam -n" after manually executing the shown commands: takes 40s,
> prints nothing, then aborts
> 
> in neither case does it print "...patience...". Building some subdirs
> with only part of the targets works.
> 
> Setup:
> OS: AIX 5.3
> Tool: gcc-4.6
> Bjam: from Boost 1.49.0
> 
> How shall I debug bjam in this case? Are there some built in limits to
> the size of the project? May some internal list run over?

It's most likely running out of memory.
Can you try using trunk Boost.Build/bjam?
There are several optimizations that
reduce memory usage.

> Can I easily
> build a debug version of bjam that I can run using gdb or something?
> 

cd tools/build/v2/engine
./build.sh --debug

In Christ,
Steven Watanabe