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

in-tree Berkeley DB (was: Re: .autogen.sh error for svn revision 8113)

From: Garret Wilson <garret_at_globalmentor.com>
Date: 2003-12-29 19:14:37 CET

I'm beginning to remember why I despise Red Hat and RPMs.

It turns out Red Het 7.0 has a gcc bug. (See
and http://rhn.redhat.com/errata/RHBA-2000-079.html ). I finally found
appropriate RPMs, but because of dependencies, I had to install glibc,
glibc-common, and glibc-devel. (I have no idea what this did to my glibc
I had already installed from the source.)

Python 2 then compiled. Subversion autogen.sh then worked correctly.

However, when trying to configure Subversion:

./configure --with-libs=/usr/local/ssl --with-ssl
--with-apr=/usr/local/apache2 --with-apr-util=/usr/local/apache2

I now get:

configure: Apache Portable Runtime (APR) library configuration
checking for APR... yes
checking APR version... 0.9.5
configure: Apache Portable Runtime Utility (APRUTIL) library configuration
checking for APR-util... yes
checking APR-UTIL version... 0.9.5
configure: error: Configuring against an in-tree copy of Berkeley DB is no
                   longer supported. Berkeley DB must be separately
                   and perhaps specified by adding --with-berkeley-db=PATH

I've never used an in-tree copy of Berkeley DB, as far as I know, and as
you can see I *am* using the --with-berkeley-db switch.

I never new upgrading could be so difficult...


Garret Wilson wrote:

> I did a svn up to revision 8113 and then ran ./autogen.sh (the same as
> I've done for previous revisions). I get:
> buildcheck: checking installation...
> buildcheck: autoconf version 2.57 (ok)
> buildcheck: autoheader version 2.57 (ok)
> buildcheck: libtool version 1.4.3 (ok)
> buildcheck: neon version 0.24.4 (ok)
> Copying libtool helper: /usr/share/aclocal/libtool.m4
> Creating getdate.c...
> subversion/libsvn_subr/getdate.y contains 10 shift/reduce conflicts.
> Creating build-outputs.mk...
> File "./gen-make.py", line 159
> print >> opt_conf, "[options]"
> ^
> SyntaxError: invalid syntax
> ERROR: gen-make.py failed
> I've upgraded neon. I've upgraded Berkeley DB. I've upgraded Apache.
> Perhaps I need to also upgrade Python, even though Python 1.5.2-27 has
> worked fine for me for all earlier svn revisions.
> So I downloaded Python 2.3.3, ran configure, and then make:
> gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
> -Wstrict-prototypes -I. -I./Include -DPy_BUILD_CORE -o Modules/python.o
> Modules/python.c
> In file included from Include/Python.h:48,
> from Modules/python.c:3:
> Include/pyport.h:554:2: #error "LONG_BIT definition appears wrong for
> platform (bad gcc/glibc config?)."
> make: *** [Modules/python.o] Error 1
> Grrr...
> Before I go further---is my original problem really because of my early
> Python version?
> Garret
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 29 19:15:22 2003

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.