apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Covener <cove...@gmail.com>
Subject Re: [VOTE] Release apr-0.9.19 and/or apr-util-0.9.18
Date Mon, 11 Oct 2010 15:33:26 GMT
> "It has in it": where? It is ncluded in the path APRUTIL_LDFLAGS, but those
> are actually not really used (only for make check and even there it works
> with the wrong path).

My make check fails with the implicit builtin expat, similar to
Sander's report (although his really was on link of aprutil itself)

/bin/sh /tmp/aprtest-25297-64/apr-0.9.19/libtool --silent --mode=link
gcc -m64 -g -O2 -pthread   -DHAVE_CONFIG_H -DLINUX=2 -D_REENTRANT
-D_GNU_SOURCE   -I/tmp/aprtest-25297-64/apr-util-0.9.18/include
-I/tmp/aprtest-25297-64/apr-util-0.9.18/include/private
-I/tmp/aprtest-25297-64/apr-0.9.19/include
-I/tmp/aprtest-25297-64/apr-util-0.9.18/xml/expat/lib  -version-info
9:19:9    -o testdbm
-L/tmp/aprtest-25297-64/apr-util-0.9.18/xml/expat/lib -no-install
testdbm.lo ../libaprutil-0.la
/tmp/aprtest-25297-64/apr-util-0.9.18/xml/expat/lib/libexpat.la
/tmp/aprtest-25297-64/apr-0.9.19/libapr-0.la -lrt -lm -lcrypt -lnsl
-lpthread -ldl
libtool: link: cannot find the library
`/tmp/aprtest-25297-64/apr-util-0.9.18/xml/expat/lib/libexpat.la' or
unhandled argument
`/tmp/aprtest-25297-64/apr-util-0.9.18/xml/expat/lib/libexpat.la'
make[1]: *** [testdbm] Error 1
make[1]: Leaving directory `/tmp/aprtest-25297-64/apr-util-0.9.18/test'
make: *** [check] Error 2
covener@miser:/tmp/aprtest-25297-64/apr-util-0.9.18> cat config.nice
#! /bin/sh
#
# Created by configure

CC="gcc -m64"; export CC
"./configure" \
"--prefix=/tmp/aprtest-25297-64/built" \
"CC=gcc -m64" \
"--with-apr=../apr-0.9.19" \
"$@"


> For Sander's build it seems libaprutil gets actually linked against libexpat
> explicitely (and then libexpat is looked for in the wrong directory). My
> Unix/Linux builds do not link libaprutil explicitely against libexpat
> (neither for recent apr-util, not for earlier 0.9 releases). This differs
> from 1.3, where libaprutil is linked against libexpat.

Thanks for the explanation. I didn't realize it didn't link directly
with expat as most of my interaction was in 1.2.x where the aprutil
itself blows up if something is wrong with expat.

I was just seeing obvious incorrect path in
APRUTIL_LIBS/APRUTIL_EXPORT_LIBS as referenced without understanding
how they were later used.

-- 
Eric Covener
covener@gmail.com

Mime
View raw message