On Tuesday 03 January 2006 10:38, Oliver.Kowalke@infineon.com wrote:
But anyway:
command 'bjam --prefix=/opt/boost "-sTOOLS=gcc" "-sSUFDLL=.sl" "-sBUILD=release <threading>multi <cxxflags>-fpic" install'
produces:
- an segmentation fault while loading the signals library! (see my previous email '[boost] bug in signals library? - segmentation fault(onlylinked) -> exit(11) called')
- libraries iostreams and wave have only extension *.a (no *.sl)
command 'bjam --prefix=/opt/boost "-sTOOLS=gcc" "-sBUILD=release <threading>multi <cxxflags>-fpic" install'
- segmentation fault disappears
- library wave is build with *.a extension only (no *.so) ....
It seams that boost build system has some problems! Please don't ignore this as you did before!
What are the problems, specifically? - Absense of ".so"/".sl" files of Wave can be explained by the fact that DLL rules were added to Jamfile on 2005-11-21. Do you have a later version? - Segmentation fault in boost.signals can be caused by anything. If you believe it's a bug in Boost.Build, you can do the following - Remove all build object of Boost.Signals - Run "bjam --with-signals -obuild.sh" from boost root (adding -sBUILD option to match the variant you're using) - The create build.sh has build commands. Take a look at them and determine if any options are wrong and are the reason for failure. Remove/change the options and verify that rebuilding by running build.sh gets you a library that does not crash. - Tell us which options you changed/removed/added. This requires a bit of work on your side, but I don't think there are many users of HP/UX here. - Volodya
Regards,
Oliver