Attempting to link against the libmongoclient.a provided in the 1.2.0 and 1.2.1 release tarballs yield unresolved externals when using a different version of boost. This is apparently expected, and I was encouraged to compile it myself.

The crux of the matter is that compiling the client lib shouldn't require spidermonkey. A simple hacky change to the SConstruct file:

diff --git a/SConstruct b/SConstruct
index 5d0b835..5029467 100644
--- a/SConstruct
+++ b/SConstruct
@@ -260,8 +260,8 @@ if ( usesm and usejvm ):
     print( "can't say usesm and usejvm at the same time" )
     Exit(1)
 
-if ( not ( usesm or usejvm or usev8 ) ):
-    usesm = True
+#if ( not ( usesm or usejvm or usev8 ) ):
+#    usesm = True
 
 if GetOption( "extrapath" ) is not None:
     for x in GetOption( "extrapath" ).split( "," ):
 
 

compiles fine and links into a program fine. Its obviously not the right fix, but it does show that it isn't actually used in the client code.

In addition, perhaps libmongoclinet.a shouldn't be distributed in the tarballs, or it should at least specify which version of boost it was compiled against.