Gabriela Gibson wrote on Mon, Mar 04, 2013 at 22:33:23 +0000:
> On 04/03/13 19:44, Daniel Shahaf wrote:
> > Do you use the system's apr (e.g., /usr/lib/libapr-1.so) or compile your
> > own? If the former you should install the "apr-dev" (or similar)
> > package, if the latter it appears you need to pass --with-apr to
> > serf/serfmake (or serf/configure if you use that).
> I guess I should tell you how my setup looks. I'm possibly repeating
> stuff from earlier emails, because I'm trying to put all the info in
> one place.
> Beyond this, I've been working with a trunk and the dependencies as
> downloaded by get-deps.sh - pretty much the classic minimal dev env.
> I chose to do this, because I thought one way to assist the project
> was to look through the eyes of someone coming new to Subversion dev
> as much as possible.
Good call. get-deps.sh is not something most devs use day-to-day, so
it's liable to bitrot.
> What I've also found during my experiments at the weekend is that
> apr-related entries in LD_FLAGS are edited while configure runs. So:
> LD_FLAGS="-L/usr/local/serf/lib -L/usr/local/apr/lib" ./configure \
> --enable-maintainer-mode --with-serf=/usr/local/serf
> failed. Examining config.log showed that the failure appeared to occur
> in the link test, and that the entry for "-L/usr/local/apr/lib" has been
Which link test was it? It's hard to make any comment about the
situation without seeing the code and the reason it strips -L flags.
(Is that our code, or something in autoconf's m4 library, that strips
the -L flags?)
> The only way I could make the serf link test pass (and also add that
> "-L/usr/local/apr/lib" flag) was to supply "--with-apr --with-apr-util" and
> that was what my patch documented.
That's.. odd. Adding "--with-apr" (without argument) should actually be
a no-op, since APR is a mandatory dependency.
> Whether this is "undocumented behaviour", "a bug in the build system",
> "there is a need to document a requirement for apr-dev", or "my
> retarded/invalid build environment" I don't feel sufficiently
> experienced to judge. I just thought - this isn't right, so submit a
Yeah, I agree something is wrong, I'm just not sure your patch is the
> It might not be the correct fix :)
> Ben wrote
> > In your case if you've installed serf in /usr/local/serf, I'd try
> > building without any --with-serf option or --with-serf=yes. Failing
> > that try the same build but with the following environment variable
> > set:
> > export PKG_CONFIG_PATH=/usr/local/serf/lib/pkgconfig
> I'm not familiar with pkgconfig, so I need to educate myself.
> I tried yesterday without any option, and serf isn't tested for.
> I've also tried the --with-serf=yes suggestion:
> g_at_musashi:~/trunk3$ ./configure --with-serf=yes --enable-maintainer-mode
> This failed (as in configure warned that serf hadn't been found).
> I've further tried with the variable:
> export PKG_CONFIG_PATH=/usr/local/serf/lib/pkgconfig
> ./configure --with-serf=yes --enable-maintainer-mode
> and this succeeds.
/me learnt something new :)
Received on 2013-03-04 23:58:25 CET