Robert Ramey wrote:

The current state of the boost serialization library in different of compiler/library/os combinations is best appreciated by reviewing our current test matrix:

http://www.meta-comm.com/engineering/boost-regression/developer/serializatio n.html

Most problems, including the one referred to above, seem to be related build issues such as compile and linking switches. The bjam system minimizes these in our test environment. I would suggest building the libraries with bjam to address the above issues.

we are using bjam for 1.32.0 not ever having built boost before i am not 100% sure it is done right (im more of a windows user (boost wise) that includes a few headers, never built the libs on windows) i can show you the command lines used, i went over the docs, and *to me* it seems fine, but apparently this isn't really the case the build process will also display the

actual command used for building and linking which can be compared to one's own setup.

Good Luck

Robert Ramey

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

BOOSTJAM=./tools/build/jam_src/bin.linux${arch}/bjam BOOST_TOOLSET="gcc" python_version # Build bjam, a jam variant, which is used instead of make cd ${S}/tools/build/jam_src ./build.sh ${BOOST_TOOLSET} || die "Failed to build bjam" cd ${S} # actual build ${BOOSTJAM} \ -sBOOST_ROOT=${S} \ -sPYTHON_ROOT=/usr \ -sPYTHON_VERSION=${PYVER} \ -sTOOLS=${BOOST_TOOLSET} \ --prefix=${D}/usr \ --layout=system \ stage || die "stage failed" ${BOOSTJAM} ${MAKEOPTS} \ -sBOOST_ROOT=${S} \ -sPYTHON_ROOT=/usr \ -sPYTHON_VERSION=${PYVER} \ -sTOOLS=${BOOST_TOOLSET} \ --prefix=${D}/usr \ --layout=system \ install || die "install failed" where ${S} is the source dir of boost as it is unpacked in a temporary location in gentoo

I use Linux. To compile the serialization examples I had to add 2 things to the provided Jamfile in 1.32.0: - the demo_pimpl_A.cpp source file. - the pthread.a library Daniel Goller wrote:

Daniel Goller wrote:

...

Robert Ramey wrote:

...

The current state of the boost serialization library in different of compiler/library/os combinations is best appreciated by reviewing our current test matrix:

http://www.meta-comm.com/engineering/boost-regression/developer/serializatio

n.html

Most problems, including the one referred to above, seem to be related build issues such as compile and linking switches. The bjam system minimizes these in our test environment. I would suggest building the libraries with bjam to address the above issues.

we are using bjam for 1.32.0

not ever having built boost before i am not 100% sure it is done right (im more of a windows user (boost wise) that includes a few headers, never built the libs on windows)

i can show you the command lines used, i went over the docs, and *to me* it seems fine, but apparently this isn't really the case

the build process will also display the

...

actual command used for building and linking which can be compared to one's own setup.

Good Luck

Robert Ramey

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

BOOSTJAM=./tools/build/jam_src/bin.linux${arch}/bjam BOOST_TOOLSET="gcc"

python_version # Build bjam, a jam variant, which is used instead of make cd ${S}/tools/build/jam_src ./build.sh ${BOOST_TOOLSET} || die "Failed to build bjam" cd ${S}

# actual build ${BOOSTJAM} \ -sBOOST_ROOT=${S} \ -sPYTHON_ROOT=/usr \ -sPYTHON_VERSION=${PYVER} \ -sTOOLS=${BOOST_TOOLSET} \ --prefix=${D}/usr \ --layout=system \ stage || die "stage failed"

${BOOSTJAM} ${MAKEOPTS} \ -sBOOST_ROOT=${S} \ -sPYTHON_ROOT=/usr \ -sPYTHON_VERSION=${PYVER} \ -sTOOLS=${BOOST_TOOLSET} \ --prefix=${D}/usr \ --layout=system \ install || die "install failed"

where ${S} is the source dir of boost as it is unpacked in a temporary location in gentoo

------------------------------------------------------------------------

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

any other suggestions on why boost built by bjam ends up with linker errors compiling the serialization demo.cpp of boost?

------------------------------------------------------------------------

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Maximilian Wilson wrote:

Perhaps this is obvious, but it wasn't to me from Boost's documentation: you have to explicitly link in the serialization library. On gcc this would be

g++ myProgram.cpp -o myProgram -lboost_serialization-gcc

(where libboost_serialization-gcc.a is a file in your library directory $LIBRARY_PATH).

Max

On Sat, 22 Jan 2005 18:07:38 -0600, Daniel Goller <morfic@gentoo.org> wrote:

...

are there any problems with boost serialization including linker errors or does this indicate a broken install

i have heard of problems with boost serialization but do not know which they might be

before running off in the wrong direction i figured i would gather information here to solve this:

http://bugs.gentoo.org/show_bug.cgi?id=78043

problem

any help on this will be appreciated

Daniel

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

i didnt explicitly provde the command line as it was shown on the bug url i provided, thanks anyway, i still got the suggestion about the "Jamfile" needing two more things, as sorry mostly windows boost user i never had to build boost before and am not immediately aware how the Jamfiles are used, come the weekend i will extend my rtfm and look into Jamfiles used during install thank you Daniel