On Thu, Jan 15, 2009 at 04:24:21PM -0700, Jeremy Whitlock wrote:
> How did you configure? Before just reverting the change, it might
> make sense to know how this was manifested.
As discussed on IRC, I build statically and you didn't.
Here's the config.log diff I promised, not much insight though,
it's just showing that using .la files works and not using them
does not. I removed hunks caused by simple tempfile name changes
(config.log.broken is created by current trunk, the config.log
was created by trunk with r35262 reverted)
--- config.log.broken Thu Jan 15 23:32:55 2009
+++ config.log Thu Jan 15 23:35:59 2009
@@ -1454,7 +1454,7 @@
-NEON_LIBS='-L/home/stsp/svn/prefix/neon/lib -lneon -lssl -lcrypto -lz -lexpat'
@@ -1508,7 +1508,7 @@
Here's the content of libserf-0.la:
# libserf-0.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.5.26 (1.1220.2.493 2008/02/01 16:58:18)
# Please DO NOT delete this file!
# It is necessary for linking the library.
# The name that we can dlopen(3).
# Names of this library.
# The name of the static archive.
# Libraries that this one depends upon.
dependency_libs=' -lcrypto -lssl -lz /usr/local/lib/libaprutil-1.la /usr/local/lib/libapr-1.la /usr/local/lib/libiconv.la -lexpat /usr/local/lib/db4/libdb.la -L/usr/local/lib -L/usr/local/lib/db4'
# Version information for libserf-0.
# Is this an already installed library?
# Should we warn about portability when linking against -modules?
# Files to dlopen/dlpreopen
# Directory that this library needs to be installed in:
Received on 2009-01-16 00:43:54 CET