Re: [boost] [filesytem].[aix].[1_34_0] related issue
"Gaurav Jain-SJR" <Gaurav.Jain <at> iflexsolutions.com> wrote on
11/19/2007
Thanks a lot this solved my problem. I am also facing another problem
while building boost. If I build it with the following command :
$bjam --v2 install toolset=vacpp --prefix=$HOME/1_34_0/32
--builddir=$HOME/tmp variant=release runtime-link=static,shared
threading=single,multi --without-python Jamfile.v2
vacpp.compile.c++
bin.v2/libs/wave/build/vacpp/release/link-static/runtime-link-static
/instantiate_cpp_grammar.o
Build seems to me hanging after this. Though I am not facing a same
problem if I specify the every target library to be built with bjam
command.
Frequently this type of problem is as a result of bjam's memory usage,
try
"export LDR_CNTRL=MAXDATA=0x80000000" in your environment. This should
make the problem go away if the issue you are having is indeed related to
bjams memory use.
I am not afraid to say its need more than this. After exporting the above mentioned environment variable I issued a fresh build, but it lead me to the same result. I am using the bjam 3.1.14 version for the build purpose. Should I upgrade to bjam 3.1.15? I come to know from boost mailing list a lot of patches and new features are gone into newest BJAM version. One such patch is I found through the mailing list discussion is Set MAXLINE in jam.h to 23k bytes for AIX. The piecemeal archive action was broken with the default MAXLINE of 102400. Because the AIX shell uses some of the 24k default buffer size for its own use, I reduced it to 23k. -- Noel B.: http://lists.boost.org/boost-build/2007/09/17386.php Is this causing the problem? BTW what's LDR_CNTRL for? :-) Regards, Gaurav Jain "There are two ways to write error-free programs; only the third works." -Alan J. Perlis DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.
participants (1)
-
Gaurav Jain-SJR