[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Configure having problems finding DB4.0.14

From: Joseph Dane <jdane_at_studio3511.com>
Date: 2002-01-09 22:49:36 CET

Owen Landgren <olandgren@Macalester.edu> writes:

> I'm stumped. What am I doing wrong? Adding a / after the directory
> path for the DB didn't help, and neither did letting configure try to
> find it by itself.
>
you're not doing anything wrong. I just ran into the same thing.

the problem is that the svn build scripts expect a shared DB library
to be built, but only the static version gets built. this despite
passing '--disable-shared' to the subversion config.

the solution, for me, was to let the build fail, then go into the DB
directory and manually build the shared version of the library, and
then restart the subversion build. e.g.

 subversion-r727 > make

... eventually fails

 subversion-r727 > cd db/dist
 dist > make libdb-4.0.la
 
... makes the shared library

 dist > cd ../..
 subversion-r727 > make

... subversion builds successfully.

I haven't done too much poking at this point, but I think the
top-level subversion Makefile is wrong at this point:

(line 153)
# recursive targets to handle external projects (e.g. APR, Neon)
external-all external-clean external-distclean external-install:
        @target=`echo $@ | sed s/external-//`; \
        list='$(EXTERNAL_PROJECT_DIRS)'; \
        for i in $$list; do \
            echo "------ making $$target in $$i"; \
            (cd $$i && $(MAKE) $$target) || exit 1; \
            echo "------ completed $$target in $$i"; \
        done;

this makes the wrong target in the DB directory.

-- 
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:55 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.