xlc boost without bzip2 support - Unresolved symbols
Hi Team, I built boost 1.40 iostream lib with xlc 6.0: setenv NO_BZIP2 1 setenv NO_ZLIB 1 bjam -d+2 --prefix= .... boost/aix64 --with-thread toolset=vacpp cflags="-q64 " cxxflags="-q64" link=shared linkflags="-q64" threading=multi --with-iostreams --layout=versioned install Even when I attempt to build without bzip2 support, why am I getting unresolved symbols at run time of executable linked? Am i missing something here? rtld: 0712-001 Symbol BZ2_bzCompressEnd was referenced from module ....stage-O/lib/aix64/libboost_iostreams-xlc-mt-1_40.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol BZ2_bzDecompressEnd was referenced from module ....stage-O/lib/aix64/libboost_iostreams-xlc-mt-1_40.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol BZ2_bzCompress was referenced from module .... aix64/libboost_iostreams-xlc-mt-1_40.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol BZ2_bzDecompress ....stage-O/lib/aix64/libboost_iostreams-xlc-mt-1_40.so was referenced from module ...stage-O/lib/aix64/libboost_iostreams-xlc-mt-1_40.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol BZ2_bzCompressInit was referenced from module ..stage-O/lib/aix64/libboost_iostreams-xlc-mt-1_40.so(), but a runtime definition of the symbol was not found. Thanks in advance, Radha
Radha wrote:
Hi Team,
I built boost 1.40 iostream lib with xlc 6.0: setenv NO_BZIP2 1 setenv NO_ZLIB 1 bjam -d+2 --prefix= .... boost/aix64 --with-thread toolset=vacpp cflags="-q64 " cxxflags="-q64" link=shared linkflags="-q64" threading=multi --with-iostreams --layout=versioned install
Even when I attempt to build without bzip2 support, why am I getting unresolved symbols at run time of executable linked? Am i missing something here? Please try bjam -s"NO_BZIP2=1" -s"NO_ZLIB=1" ... The "variables" referred in the iostreams documentation are Boost.Build variables, not environment variables. The latest docs do state this, but still give no example how to set the variables on command line.
Cheers, Mikko
participants (2)
-
Mikko Vainio
-
Radha