This problem remains in the boost_1_32_0 release, and is slightly more complex/different than I've previously reported. I got all the serialization examples to build by: 1. Placing /usr/lib/libm.a on my system. The static development libraries where not on by default. 2. Putting a <library-file>/usr/lib/libpthread.a statement in the requirements section of the common rule defined in the Jamfile. This brings up a number of questions: First, is it possible to mix static and shared libraries? In attempting to use libpthread.so instead of libpthread.a, These errors occurred: /lib/libpthread.so.0: undefined reference to `_errno@GLIBC_2.0' /lib/libpthread.so.0: undefined reference to `_h_errno@GLIBC_2.0' I've attempted to add /usr/lib/glib-2.0.so, but this has no affect. Second, where did the requirement to have libm.a come from? Neither the serialization library Jamfile or the example Jamfile makes reference to it. Last, I see that the serialization library Jamfile has a <runtime-link>static/dynamic statement in its default build section. So why isn't there a shared library for serialization? FYI. I've switched to gcc v3.4.3 recently. Everything that I know about involving the boost libraries remained the same. Jeffrey Holle wrote:
My boost libaries come from CVS on Sun Nov 14 18:35:14 EST 2004 I'm building with gcc v3.4.2 on a linux system.
I've run into a problem in attempting to build the serialization examples. All failed in link phase with: /usr/bin/ld: cannot find -lm