Boost logo

Boost-Build :

From: Marty Fried (public.forums_at_[hidden])
Date: 2007-10-11 11:26:00

Thanks for the reply. I hope my information will be helpful.

"Vladimir Prus" <ghost_at_[hidden]> wrote in message
> Marty Fried wrote:
>> When I try to build the libraries using the vacpp and install option, I
>> get
>> a segmentation fault within about 1 minute. I got this both when I used
>> the defaults (gcc was picked), and when I reinstalled and used vacpp.
> Segmentation fault of what? bjam, or compiler, or something else?
I'm not really sure - do you know how I can tell? All I see externally is:
(-----console output-----)
# ./tools/jam/src/bin.aixppc/bjam --toolset=vacpp 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).
Segmentation fault (core dumped)

Is there any sort of debug mode for bjam, or log file, or something I can
look at? I'm just starting out with, and it's hard to learn everything at
(well, actually, it's hard to learn everything period).

>> Next, I used the stage option, and I don't get the core dumps. I let it
>> run
>> overnight, and today, xlCentry was stalled after running 681 minutes.
>> So,
>> I
>> killed it and let it continue. It stalled a couple more times, and
>> finally finished with a bunch of bash errors, and I have about 75 files
>> in
>> the
>> stage/lib directory. I don't see some, such as filesystem, so I'm not
>> sure if I have a good build.
> What's xlCentry? What bash errors?

I believe xlCentry does the actual compile.

When it stalled, the last line I saw on the console was:

I did a ps command each time, but it wasn't until the third time it stalled
that I learned
how to get a full, untruncated command line...
bjam was running with this commandline:
./tools/jam/src/bin.aixppc/bjam --toolset=vacpp stage

and xlC was running with this commandline:
xlC -c -DBOOST_ALL_NO_LIB=1 -DNDEBUG -qcpluscmt -O3
-qstrict -qfuncsect -qeh -qrtti -I. -o bin.v2/libs/wave/build/vacpp/release/

For what it's worth, the xlCentry commandline was:
/usr/vacpp/exe/xlCentry -D_THREAD_SAFE -D__VACPP_MULTI__ -D_AIX
-D_AIX32 -D_AIX41 -D_AIX43 -D_AIX50 -D_AIX51 -D_AIX52 -D_AIX53
-qosvar=aix.5.3 -qalias=ansi -qthreaded -qcpluscmt -O3 -qstrict -qfuncsect -qeh
-qasm_as=/bin/as -obin.v2/libs/wave/build/vacpp/release/link-static/threading-multi/instantiate_cpp_grammar.o
/tmp/xlcW0uCabEa /tmp/xlcW1uCabEb /dev/null instantiate_cpp_grammar.lst
/dev/null /tmp/xlcW2uCabEc

Maybe someone more familiar with aix will have a clue from that.

If you have any suggestions, or need more info, please let me know.
I'll try my best to find out more on my end.


Marty Fried public.forums_at_[hidden]
Left Coast, USA.

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at