[Boost-build] [v2] Bjam patch for vacpp

From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2006-09-25 17:27:04

Hi,

Bjam is unable to build our applications on our IBM using xlC 7.1.   
By default, the IBM limits available stack to 256 Mb.  For some of  
our applications, this is inadequate.  I'd like to patch the tools/ 
jam/src/build.jam for vacpp to permit bjam to use a larger memory  
segment by default.  If we do this, it will help avoid failures  
building Boost in the future as the number and size of Boost  
libraries grows.

This is the behavior building one of our applications without the  
patch applied.

 > bjam --v2 vacpp
Illegal instruction (core dumped)

I'd like to add -bmaxdata:0x40000000 to the debug and release build  
options for vacpp in build.jam.  A description of what this option  
does from the xlC man page.

          -bmaxdata=<num>
                 Sets the maximum size of the area shared by the
                 static data (both initialized and uninitialized)
                 and the heap to <num> bytes.  The default is
                 -bmaxdata=0.

Can someone review this patch and, if it's acceptable, commit it to  
the head of the repository?  If I don't hear from anyone if a few  
days, I'll assume it's okay to commit it myself.

Thanks.

-- Noel Belcourt