How to enable GMP on freebsd? - installation

I installed swi-prolog as below:
$./configure --prefix=/home/***/swi-prolog/ --enable-gmp
$gmake && gmake check && gmake install
however, it still reports no GMP syupport:
?- random(33).
Warning: This version of SWI-Prolog is not compiled with GMP support.
Warning: Floating point random operations are not supported.
ERROR: is/2: Arithmetic: `random_float/0' is not a functionenter code here
$find /usr/local/lib -name "libgmp*"
/usr/local/lib/libgmp.so.10
/usr/local/lib/libgmp.so
/usr/local/lib/libgmp.la
/usr/local/lib/libgmpxx.so.6
/usr/local/lib/libgmpxx.so
/usr/local/lib/libgmpxx.la
/usr/local/lib/libgmp.a
/usr/local/lib/libgmpxx.a
I am using FreeBSD and swi-prolog is stable release http://www.swi-prolog.org/download/stable/src/pl-6.2.6.tar.gz .
Any suggestion is appreciated !

It is fixed by set CFLAGS and LDFLAGS:
$echo $LDFLAGS
-L/usr/local/lib
$echo $CFLAGS
-I/usr/local/include
$./configure --prefix=/home/sw2wolf/swi-prolog/ --enable-gmp
$gmake && gmake install
$ldd ~/swi-prolog/lib/swipl-6.3.8/bin/i386-freebsd9.0/swipl
**libgmp.so.10** => /usr/local/lib/libgmp.so.10 (0x2815b000)
libexecinfo.so.1 => /usr/local/lib/libexecinfo.so.1 (0x281b9000)
librt.so.1 => /usr/lib/librt.so.1 (0x281c4000)
libreadline.so.6 => /usr/local/lib/libreadline.so.6 (0x281ca000)
libncursesw.so.5.9 => /usr/local/lib/libncursesw.so.5.9 (0x281ff000)
libm.so.5 => /lib/libm.so.5 (0x28229000)
libthr.so.3 => /lib/libthr.so.3 (0x28243000)
libc.so.7 => /lib/libc.so.7 (0x28264000)
libncurses.so.8 => /lib/libncurses.so.8 (0x28383000)
libtinfow.so.5.9 => /usr/local/lib/libtinfow.so.5.9 (0x283c3000)
Regards!

Related

Ffmpeg ./configure not found

I'm trying to install ffmpeg with libvpx & libx264 on my vps. Centos07. I've followed these instructions https://trac.ffmpeg.org/wiki/CompilationGuide/Centos to the T.
Now when I try to run
cd ~/ffmpeg; ./configure --enable-libvpx --enable-gpl --enable-libx264
it returns
-bash: ./configure: No such file or directory
When I try ffmpeg -v
ffmpeg: error while loading shared libraries: libx264.so.148: cannot open shared object file: No such file or directory
and ldd $(which ffmpeg) returns
root#host [~/ffmpeg_sources]# ldd $(which ffmpeg)
linux-vdso.so.1 => (0x00007fff4fb86000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f4972e27000)
libxcb-shm.so.0 => /lib64/libxcb-shm.so.0 (0x00007f4972c23000)
libxcb-xfixes.so.0 => /lib64/libxcb-xfixes.so.0 (0x00007f4972a1a000)
libxcb-shape.so.0 => /lib64/libxcb-shape.so.0 (0x00007f4972816000)
libx264.so.148 => not found
libm.so.6 => /lib64/libm.so.6 (0x00007f4972513000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f49722ee000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f49720de000)
libz.so.1 => /lib64/libz.so.1 (0x00007f4971ec7000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4971cab000)
libc.so.6 => /lib64/libc.so.6 (0x00007f49718e9000)
libXau.so.6 => /lib64/libXau.so.6 (0x00007f49716e4000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4973056000)
I've followed all the instructions exactly - is there something I'm missing?

Using PSPP-Perl-Module on Ubuntu 12.04

I want to use the PSPP-Perl-Module, but it seem to be much harder than expected. I would be fine using any version of the module, but since it seems like one has to build it on every mashine (please correct my if I am wrong) I go for Ubuntu LTS versions:
pspp-0.7.9+git20120319 is the PSPP version in Ubuntu LTS 12.04.
First try: CPAN install
cpan PSPP:Sysfile
Will build a pretty old version
CPAN.pm: Going to build P/PD/PDONELAN/PSPP-Perl-0.7.2.20090730.tar.gz
and asks for a configured source directory which I don't have at the moment.
Enter the location of the build directory of the configured pspp source: []
Second try: apt-get source -b
cd ~
apt-get build-dep pspp
apt-get source -b pspp
Downloads the source of 0.7.9+git20120319 into the current directory and builds it. Building seems to work for quite a while but ends with an error in test phase:
...
| configure:43806: $? = 0
| configure:43806: gcc -std=gnu99 -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Wdeclaration-after-statement -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pango-1.0 conftest.c >&5
| conftest.c: In function 'main':
| conftest.c:444:22: error: expected expression before ')' token
| configure:43806: $? = 1
| configure: failed program was:
| | /* confdefs.h */
...
| This file was extended by GNU PSPP config.status 0.7.9, which was
| generated by GNU Autoconf 2.68. Invocation command line was
|
| CONFIG_FILES =
| CONFIG_HEADERS =
| CONFIG_LINKS =
| CONFIG_COMMANDS =
| $ ./config.status config.h
|
| on agnes
|
| config.status:2635: creating config.h
make[1]: *** [override_dh_auto_test] Fehler 1
make[1]: Verlasse Verzeichnis '/root/pspp-0.7.9+git20120319'
make: *** [build] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2
Build-Befehl »cd pspp-0.7.9+git20120319 && dpkg-buildpackage -b -uc« fehlgeschlagen.
E: Kindprozess fehlgeschlagen
The PSPP users mailinglist discussed some problems building the Perl-Module this January, and I quote:
Basically you are right, you will need to compile PSPP first, but you don't need
to install it. At a risk of contradicting that sentence, you should follow the
instructions in the file called INSTALL. However, to save yourself a bit of
time and from having to install lots of things you won't need, you can pass
various --without-* flags to configure, thus:
./configure --without-gui --without-cairo --without-libncurses
make
cd perl-module
make install
So with my unfinished build I entered the perl-module directory
cd pspp-0.7.9+git20120319/perl-module
make install
Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /usr/lib/perl/5.14.2/auto/PSPP/PSPP.so
Installing /usr/lib/perl/5.14.2/auto/PSPP/PSPP.bs
Installing /usr/lib/perl/5.14.2/PSPP.pm
Installing /usr/man/man3/PSPP.3pm
Installing /usr/man/man3/PSPP::Examples.3pm
Appending installation info to /usr/lib/perl/5.14.2/perllocal.pod
Long story short: Still no success using the perl-module:
#!/usr/bin/perl
use PSPP;
Can't load '/usr/local/lib/perl/5.14.2/auto/PSPP/PSPP.so' for module PSPP: libpspp-core-0.7.9.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden at /usr/share/perl/5.14/XSLoader.pm line 71.
at /usr/local/lib/perl/5.14.2/PSPP.pm line 26
BEGIN failed--compilation aborted at /usr/local/lib/perl/5.14.2/PSPP.pm line 27.
Compilation failed in require at ./test2.pl line 2.
BEGIN failed--compilation aborted at ./test2.pl line 2.
:-(
The file PSPP.so in question exists:
ls /usr/local/lib/perl/5.14.2/auto/PSPP
libpspp-0.7.9.so libpspp-core-0.7.9.so libpspp-core.so libpspp.so PSPP.bs PSPP.so
This is where I am stuck. Any hints on any approaches are very very welcome. My understanding is, that CPAN has an uploaded old version 0.7.2 of the PSPP-Module, but that the PSPP-Module is actually part of the main PSPP source. Why is the module not automatically installed on by mashine as part of apt-get install pspp. Is it? Am I too stupid to find/use it?
Many thanks in advance, Steve
Thanks to an answer on PSPP's friendy mailinglist, I found a solution:
ldd /usr/local/lib/perl/5.14.2/auto/PSPP/PSPP.so
linux-vdso.so.1 => (0x00007fffe23d2000)
libpspp-core-0.7.9.so => not found
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7b66a35000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7b6702c000)
Then I created a file
echo '/usr/local/lib/perl/5.14.2/auto/PSPP' > /etc/ld.so.conf.d/pspp.conf
ldconfig
And now it looks better!
ldd /usr/local/lib/perl/5.14.2/auto/PSPP/PSPP.so
linux-vdso.so.1 => (0x00007fff1a5ff000)
libpspp-core-0.7.9.so =>
/usr/local/lib/perl/5.14.2/auto/PSPP/libpspp-core-0.7.9.so
(0x00007f4daf913000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4daf554000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2
(0x00007f4daf1f8000)
libpq.so.5 => /usr/lib/libpq.so.5 (0x00007f4daefcb000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4daedb4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4daeab7000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4dafe06000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4dae8b3000)
libssl.so.0.9.8 => /lib/x86_64-linux-gnu/libssl.so.0.9.8
(0x00007f4dae660000)
libcrypto.so.0.9.8 => /lib/x86_64-linux-gnu/libcrypto.so.0.9.8
(0x00007f4dae2d2000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3
(0x00007f4dae004000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2
(0x00007f4dade00000)
libgssapi_krb5.so.2 =>
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f4dadbc1000)
libldap_r-2.4.so.2 =>
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f4dad972000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f4dad755000)
libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3
(0x00007f4dad52c000)
libkrb5support.so.0 =>
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f4dad324000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1
(0x00007f4dad120000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
(0x00007f4dacf03000)
liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2
(0x00007f4daccf5000)
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2
(0x00007f4dacada000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3
(0x00007f4dac89b000)
libgnutls.so.26 => /usr/lib/x86_64-linux-gnu/libgnutls.so.26
(0x00007f4dac5df000)
libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11
(0x00007f4dac361000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0
(0x00007f4dac159000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26
(0x00007f4dabed3000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8
(0x00007f4dabc33000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4
(0x00007f4dab9fe000)
libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18
(0x00007f4dab7e9000)
libtasn1.so.3 => /usr/lib/x86_64-linux-gnu/libtasn1.so.3
(0x00007f4dab5d8000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0
(0x00007f4dab3c5000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x00007f4dab1c1000)
libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0
(0x00007f4daaf98000)
libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1
(0x00007f4daad88000)
libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5
(0x00007f4daab3e000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x00007f4daa89b000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
(0x00007f4daa661000)
I can now run the example Perl code that uses the PSPP native libs.

Missing a library in ldd after using gcc -l

I'm compiling an executable called "interrogate" with:
g++ -o built/bin/interrogate -Lbuilt/lib -Lbuilt/tmp -L/usr/X11R6/lib \
built/tmp/interrogate_composite1.o built/tmp/interrogate_composite2.o \
-lp3cppParser -lp3dtool -lp3dtoolconfig -lp3pystub -pthread -ldl
After the compilation, when i try to execute the executable:
$ LD_LIBRARY_PATH=built/lib built/bin/interrogate
built/bin/interrogate: symbol lookup error: built/lib/libp3dtool.so.1.8: undefined symbol: _Py_NoneStruct
This symbol is provided by the libp3pystub.so, but the interrogate executable doesn't have any reference to this library (I did used the -lp3pystub):
$ LD_LIBRARY_PATH=built/lib ldd built/bin/interrogate
linux-vdso.so.1 => (0x00007fff2016a000)
libp3dtool.so.1.8 => built/lib/libp3dtool.so.1.8 (0x00007f498d57a000)
libp3dtoolconfig.so.1.8 => built/lib/libp3dtoolconfig.so.1.8 (0x00007f498d51b000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f498d1f2000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f498cfdc000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f498cdbf000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f498c9ff000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f498c7fb000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f498c4ff000)
/lib64/ld-linux-x86-64.so.2 (0x00007f498d5bc000)
If i manually load the libp3pystub.so, the executable works:
$ LD_PRELOAD=built/lib/libp3pystub.so LD_LIBRARY_PATH=built/lib built/bin/interrogate
Usage:
interrogate [opts] file.C [file.C ...]
interrogate -h
My question is: why the library i've added with -lp3pystub is not referenced by the interrogate executable?
I actually find the answer myself. I was compiling on Ubuntu, and they added a default optimization flags: -Wl,--as-needed. This optimization check if no symbol from the libraries passed with -l are used in the main executable, they will be removed.
And that's where my error was: _Py_NoneStruct is not directly used by interrogate, but by another shared library. So i must manually specify that the p3pystub is needed.
One possible fix would be:
$ g++ -o built/bin/interrogate -Lbuilt/lib -Lbuilt/tmp -L/usr/X11R6/lib \
built/tmp/interrogate_composite1.o built/tmp/interrogate_composite2.o \
-Wl,--no-as-needed -lp3cppParser -lp3dtool -lp3dtoolconfig -lp3pystub \
-pthread -ldl
And then i correctly got the library in the ldd output:
$ LD_LIBRARY_PATH=built/lib ldd built/bin/interrogate
linux-vdso.so.1 => (0x00007fff0edff000)
libp3dtool.so.1.8 => built/lib/libp3dtool.so.1.8 (0x00007fa1c36be000)
libp3dtoolconfig.so.1.8 => built/lib/libp3dtoolconfig.so.1.8 (0x00007fa1c365f000)
>>> libp3pystub.so.1.8 => built/lib/libp3pystub.so.1.8 (0x00007fa1c3658000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa1c342f000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa1c312c000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa1c2e2f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa1c2c19000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa1c29fc000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa1c263c000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa1c3700000)
Reference:
https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition

How do I make the linker and loader choose a shared library at a specific path?

I wrote a code for which I have a Makefile like this:
CC=gcc
CXX=g++
DEBUG=-g
COMPILER=${CXX}
#INCLUDE= -I Re2/ -I Re2/re2/
#WARN=-Wall
spambin: main.cpp Mail.o trie.o Spambin.o config.o getdns.o
${COMPILER} ${DEBUG} ${WARN} -o spambin main.cpp Mail.o trie.o Spambin.o config.o getdns.o /usr/lib/libre2.so
trie.o: trie.cpp
${COMPILER} ${DEBUG} ${WARN} -c trie.cpp ${INCLUDE}
Mail.o: Mail.cpp
${COMPILER} ${DEBUG} ${WARN} -c Mail.cpp ${INCLUDE}
config.o: config.cpp
${COMPILER} ${DEBUG} ${WARN} -c config.cpp ${INCLUDE}
Spambin.o: Spambin.cpp
${COMPILER} ${DEBUG} ${WARN} -c Spambin.cpp ${INCLUDE}
getdns.o: getdns.c
${CC} ${DEBUG} ${WARN} -c getdns.c ${INCLUDE}
clean:
rm -f *.o
The issue I'm facing is that I want my code to directly pick the /usr/lib/libre2.so.
Doing ldd on the final output binary gives:
linux-gate.so.1 => (0x00693000)
libre2.so.0 => /usr/lib/libre2.so.0 (0x00159000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x004f4000)
libm.so.6 => /lib/libm.so.6 (0x00ce8000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x002b8000)
libc.so.6 => /lib/libc.so.6 (0x00b83000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00d13000)
/lib/ld-linux.so.2 (0x00b64000)
But when I move this file to live servers and do ldd on the binary, the result is:
linux-gate.so.1 => (0x0018b000)
libre2.so.0 => /usr/local/lib/libre2.so.0 (0x00b89000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0040f000)
libm.so.6 => /lib/libm.so.6 (0x00ad2000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00c5e000)
libc.so.6 => /lib/libc.so.6 (0x0096c000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00ab9000)
/lib/ld-linux.so.2 (0x00949000)
The binary path is /usr/local/lib/libre2.so.0.
Is there any way we can force compiler to pick the .so file from our preferred path?
Yes, there is a way: you can specify full path to the shared library when linking,e.g.:
Let my library is: libtest2.so (it is in /projects/tests/test_so)
Let my main program cpp file is: main.cpp
Then:
g++ main.cpp -o test /projects/tests/test_so/libtest2.so
Produces binary test which has embedded absolute path /projects/tests/test_so in it. No matter where you move the test binary it will always look for /projects/tests/test_so/libtest2.so
Alternatively you may look at -rpath switch that you can use with gcc (actually it is a linker switch),e.g:
gcc -Wl,-rpath,'<path-to-lib-directory>'
But this approach may cause your program to look also for other shared libraries in <path-to-lib-directory> which may not be exactly what you want.

boost::asio::streambuf -- linker error

I'm having trouble getting a boost program to compile. The example I'm trying to compile is here: http://rosettacode.org/wiki/Web_scraping#C.2B.2B
This is what happens when I try to compile:
% g++ -Wall test.c -lboost_regex -lboost_system -lboost_thread
/tmp/ccJSxOji.o: In function `boost::exception_detail::error_info_injector<std::length_error>::error_info_injector(boost::exception_detail::error_info_injector<std::length_error> const&)':
test.c:(.text._ZN5boost16exception_detail19error_info_injectorISt12length_errorEC2ERKS3_[_ZN5boost16exception_detail19error_info_injectorISt12length_errorEC5ERKS3_]+0x53): undefined reference to `std::length_error::~length_error()'
/tmp/ccJSxOji.o: In function `boost::exception_detail::error_info_injector<std::length_error>::~error_info_injector()':
test.c:(.text._ZN5boost16exception_detail19error_info_injectorISt12length_errorED2Ev[_ZN5boost16exception_detail19error_info_injectorISt12length_errorED5Ev]+0x2e): undefined reference to `std::length_error::~length_error()'
collect2: ld returned 1 exit status
I think I've narrowed the problem down to this line:
boost::asio::streambuf response ;
I'm using gcc 4.6.0, linux of course:
% gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-linux-gnu/4.6.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /build/src/gcc-4.6-20110429/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --disable-multilib --disable-libstdcxx-pch --enable-checking=release
Thread model: posix
gcc version 4.6.0 20110429 (prerelease) (GCC)
Possibly related thread:
Code using boost::asio::streambuf causes segfault
I hate to answer my own question, but as it turns out, I was bitten by this: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found
I did some more digging:
% ldd /usr/lib/libboost_regex.so
/usr/lib/libboost_regex.so: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/libboost_regex.so)
linux-gate.so.1 => (0xb77b3000)
libicuuc.so.46 => /usr/lib/libicuuc.so.46 (0xb7553000)
libicui18n.so.46 => /usr/lib/libicui18n.so.46 (0xb7389000)
libicudata.so.46 => /usr/lib/libicudata.so.46 (0xb650a000)
librt.so.1 => /lib/librt.so.1 (0xb6501000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6412000)
libm.so.6 => /lib/libm.so.6 (0xb63e8000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb63cc000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb63b1000)
libc.so.6 => /lib/libc.so.6 (0xb624b000)
libdl.so.2 => /lib/libdl.so.2 (0xb6246000)
/lib/ld-linux.so.2 (0xb77b4000)
% ldd /usr/lib/libboost_date_time.so
/usr/lib/libboost_date_time.so: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/libboost_date_time.so)
linux-gate.so.1 => (0xb78cf000)
librt.so.1 => /lib/librt.so.1 (0xb788f000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb77a1000)
libm.so.6 => /lib/libm.so.6 (0xb7777000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb775b000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb773f000)
libc.so.6 => /lib/libc.so.6 (0xb75d9000)
/lib/ld-linux.so.2 (0xb78d0000)
In sum, my gcc-libs were out of date. To fix it, I did:
# pacman -Q -o /usr/lib/libstdc++.so.6
/usr/lib/libstdc++.so.6 is owned by gcc-libs 4.6.0-5
# pacman -S gcc-libs
Thanks to everyone who commented, you got me thinking in the right direction.

Resources