You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Florin Iucha <fl...@iucha.net> on 2001/12/26 05:08:59 UTC
compiling svn-588 on FreeBSD with stock neon and db3
Hello!
It's Christmas so I got more time to play :)
I have tried to install svn on my FreeBSD box. I have compiled neon and
db3 from ports and installed them.
The problem is that the configure script can't find the headers for db3
since they go in /usr/local/include/db3 instead of /usr/local/include.
The same happens with neon, but only during compilation (it somehow
passes the configure stage).
Is anybody looking into this, or should I look into it?
Merry Christmas,
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Ben Collins-Sussman <su...@collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> cool... i will update the port tonight. we do have another problem
> though. apparently the db3-latest port, which we were using for
> berkeley db, just got removed from the freebsd ports tree
Here's a little tip from one FreeBSD user to others: I never installed
any db3 ports on my system. Instead, I have a copy of db3 just
sitting in my svn tree. It's a nice way of avoiding the whole
problem. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Justin Erenkrantz <je...@ebuilt.com> writes:
> FWIW, if you have DB4 on your machine, httpd (more precisely
> apr-util) will detect it and link against it. We added that
> a few weeks ago. Let me know if you have problems on the
> httpd side of things. I think some of the auth modules may
> try to link against the DB libraries, so that may be an
> issue. -- justin
That may be the resolution of the issue I'm remembering then, great!
By the way, turns out my patch could configure after all. I had added
this to /etc/ld.so.conf
/usr/local/BerkeleyDB.4.0
instead of this:
/usr/local/BerkeleyDB.4.0/lib
before running `ldconfig'. Naturally, Subversion still couldn't find
the library. :-)
Having gotten past that step, the code portions of the patch turn out
to have a few problems, so I'm still working on it. Here's the
current iteration, which I post only in case anyone is curious -- I
will be finishing this very soon, no need for others to pick it up
unless they will complete it in the next few hours (as long as it
takes me to see the "Fellowship Of The Ring", which is where I'm
headed now, bye!)
-Karl
Upgrade to Berkeley DB 4.0.14:
This patch still in progress; run "make check" to see errors about
illegal flag specified to DBcursor->c_get.
* subversion/libsvn_fs/fs.c (cleanup_fs): Use fs->env->txn_checkpoint.
(svn_fs_close_fs): Use fs->env->txn_stat and fs->env->lock_stat, in
the instrumenting code.
* subversion/libsvn_fs/trail.c (begin_trail): Use
fs->env->txn_begin.
(abort_trail): Use trail->db_txn->abort.
(commit_trail): Use trail->db_txn->commit and fs->env->txn_checkpoint.
* INSTALL: Talk about Berkeley 4.0.14, not 3.3.11.
* ac-helpers/berkeley-db.m4 (SVN_LIB_BERKELEY_DB): Link to the .la
library unconditionally, as Berkeley now generates one. Make
workarounds look for Berkeley 4.0, not 3.3.
* configure.in (SVN_FS_WANT_DB_MAJOR, SVN_FS_WANT_DB_MINOR,
SVN_FS_WANT_DB_PATCH): Set to 4, 0, and 14 respectively.
Index: ./ac-helpers/berkeley-db.m4
===================================================================
--- ./ac-helpers/.svn/text-base/berkeley-db.m4.svn-base Mon Nov 19 15:28:02 2001
+++ ./ac-helpers/berkeley-db.m4 Wed Dec 26 17:58:35 2001
@@ -97,13 +97,7 @@
dbdir=`cd db/dist ; pwd`
SVN_DB_INCLUDES="-I$dbdir"
svn_lib_berkeley_db=yes
- # Linking directly to the .la is broken with --disable-shared
- # because Berkeley db does not seem to generate a .la library.
- if test "$enable_shared" = "yes"; then
- SVN_DB_LIBS="$dbdir/libdb-3.3.la"
- else
- SVN_DB_LIBS="-L$dbdir -ldb"
- fi
+ SVN_DB_LIBS="$dbdir/libdb-4.0.la"
elif test "$status" = "skip"; then
svn_lib_berkeley_db=no
else
@@ -115,9 +109,11 @@
# database library in /usr/local/lib, as libdb.a. There is no
# /usr/local/include/db.h. So if you check for /usr/local first, you'll
# get the old header file from /usr/include, and the new library from
- # /usr/local/lib --- disaster. Check for that bogosity first.
- places="std /usr/local/include/db3:/usr/local/lib /usr/local
- /usr/local/BerkeleyDB.$1.$2 /usr/include/db3:/usr/lib"
+ # /usr/local/lib. Disaster. We check for that bogosity first,
+ # and assume that the bogosity has carried over to the Berkeley
+ # 4.0.x series -- if it hasn't, someone please make a noise.
+ places="std /usr/local/include/db4:/usr/local/lib /usr/local
+ /usr/local/BerkeleyDB.$1.$2 /usr/include/db4:/usr/lib"
fi
# Now `places' is guaranteed to be a list of place specs we should
# search, no matter what flags the user passed.
Index: ./configure.in
===================================================================
--- ./.svn/text-base/configure.in.svn-base Fri Dec 21 11:05:35 2001
+++ ./configure.in Wed Dec 26 17:58:35 2001
@@ -116,9 +116,9 @@
# Build the filesystem library (and repository administration tool)
# only if we have an appropriate version of Berkeley DB.
-SVN_FS_WANT_DB_MAJOR=3
-SVN_FS_WANT_DB_MINOR=3
-SVN_FS_WANT_DB_PATCH=11
+SVN_FS_WANT_DB_MAJOR=4
+SVN_FS_WANT_DB_MINOR=0
+SVN_FS_WANT_DB_PATCH=14
SVN_LIB_BERKELEY_DB($SVN_FS_WANT_DB_MAJOR, $SVN_FS_WANT_DB_MINOR,
$SVN_FS_WANT_DB_PATCH)
Index: ./subversion/libsvn_fs/trail.c
===================================================================
--- ./subversion/libsvn_fs/.svn/text-base/trail.c.svn-base Mon Nov 19 15:27:58 2001
+++ ./subversion/libsvn_fs/trail.c Wed Dec 26 18:05:31 2001
@@ -52,7 +52,7 @@
trail->pool = svn_pool_create (pool);
trail->undo = 0;
SVN_ERR (DB_WRAP (fs, "beginning Berkeley DB transaction",
- txn_begin (fs->env, 0, &trail->db_txn, 0)));
+ fs->env->txn_begin (fs->env, 0, &trail->db_txn, 0)));
*trail_p = trail;
return SVN_NO_ERROR;
@@ -72,7 +72,7 @@
undo->func (undo->baton);
SVN_ERR (DB_WRAP (fs, "aborting Berkeley DB transaction",
- txn_abort (trail->db_txn)));
+ trail->db_txn->abort (trail->db_txn)));
svn_pool_destroy (trail->pool);
@@ -96,13 +96,13 @@
doesn't return DB_LOCK_DEADLOCK --- all deadlocks are reported
earlier. */
SVN_ERR (DB_WRAP (fs, "committing Berkeley DB transaction",
- txn_commit (trail->db_txn, 0)));
+ trail->db_txn->commit (trail->db_txn, 0)));
/* Do a checkpoint here, if enough has gone on.
The checkpoint parameters below are pretty arbitrary. Perhaps
there should be an svn_fs_berkeley_mumble function to set them. */
SVN_ERR (DB_WRAP (fs, "checkpointing after Berkeley DB transaction",
- txn_checkpoint (fs->env, 1024, 5, 0)));
+ fs->env->txn_checkpoint (fs->env, 1024, 5, 0)));
/* We don't destroy the pool; we assume it contains stuff which will
be useful beyond the transaction. */
Index: ./subversion/libsvn_fs/fs.c
===================================================================
--- ./subversion/libsvn_fs/.svn/text-base/fs.c.svn-base Tue Dec 18 11:51:20 2001
+++ ./subversion/libsvn_fs/fs.c Wed Dec 26 17:58:35 2001
@@ -132,12 +132,12 @@
/* Checkpoint any changes. */
{
- int db_err = txn_checkpoint (env, 0, 0, 0);
+ int db_err = env->txn_checkpoint (env, 0, 0, 0);
while (db_err == DB_INCOMPLETE)
{
apr_sleep (1000000L); /* microseconds, so 1000000L == 1 second */
- db_err = txn_checkpoint (env, 0, 0, 0);
+ db_err = env->txn_checkpoint (env, 0, 0, 0);
}
/* If the environment was not (properly) opened, then txn_checkpoint
@@ -269,8 +269,9 @@
int db_err;
/* Print transaction statistics for this DB env. */
- if ((db_err = txn_stat (fs->env, &t)) != 0)
- fprintf (stderr, "Error running txn_stat(): %s", db_strerror (db_err));
+ if ((db_err = fs->env->txn_stat (fs->env, &t, 0)) != 0)
+ fprintf (stderr, "Error running fs->env->txn_stat(): %s",
+ db_strerror (db_err));
else
{
printf ("*** DB txn stats, right before closing env:\n");
@@ -292,8 +293,9 @@
}
/* Print transaction statistics for this DB env. */
- if ((db_err = lock_stat (fs->env, &l)) != 0)
- fprintf (stderr, "Error running lock_stat(): %s", db_strerror (db_err));
+ if ((db_err = fs->env->lock_stat (fs->env, &l, 0)) != 0)
+ fprintf (stderr, "Error running fs->env->lock_stat(): %s",
+ db_strerror (db_err));
else
{
printf ("*** DB lock stats, right before closing env:\n");
Index: ./INSTALL
===================================================================
--- ./.svn/text-base/INSTALL.svn-base Thu Dec 20 16:34:19 2001
+++ ./INSTALL Wed Dec 26 17:58:35 2001
@@ -148,17 +148,17 @@
building a Subversion client that speaks to a remote (networked)
repository, you don't need it.
- You'll need Berkeley DB 3.3.11 installed on your system. You can
+ You'll need Berkeley DB 4.0.14 installed on your system. You can
get it from http://www.sleepycat.com/.
If you already have another version of Berkeley DB installed and
- don't want to downgrade, you can unpack the Berkeley 3.3.11
+ don't want to downgrade, you can unpack the Berkeley 4.0.14
distribution into a subdir named `db' in the top-level of the
Subversion source tree. Then Subversion will ignore the system
DB and use the one it found in its own source tree.
Alternatively, you can add this flag
- --with-berkeley-db=/usr/local/BerkeleyDB.3.3
+ --with-berkeley-db=/usr/local/BerkeleyDB.4.0
to your `configure' switches, and the build process will use the
named Berkeley. You may need to use a different path, of
@@ -354,11 +354,11 @@
this from happening, you have to tell Apache where to find the
version of db subversion uses. Right before configure:
- export LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib
- export CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include
+ export LDFLAGS=-L/usr/local/BerkeleyDB.4.0/lib
+ export CPPFLAGS=-I/usr/local/BerkeleyDB.4.0/include
- Add --with-dbm=db3 to the configure line. This note assumes
- you have installed Berkeley DB 3.3.11 at its default locations.
+ Add --with-dbm=db4 to the configure line. This note assumes
+ you have installed Berkeley DB 4.0.14 at its default locations.
For more info about the db requirement, see section III.C.1.
All instructions below assume you configured Apache to install
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Wed, Dec 26, 2001 at 04:22:31PM -0600, Karl Fogel wrote:
> However, I just recalled that the whole reason we delayed this upgrade
> in the first place is that there's a problem trying to use different
> Berkeley versions between Apache and Subversion -- as I remember it,
> mod_dav_svn was unable to load a different version of the Berkeley
> shared libraries than the rest of httpd 2.0, so we can't upgrade until
> Apache/APR does (?).
FWIW, if you have DB4 on your machine, httpd (more precisely
apr-util) will detect it and link against it. We added that
a few weeks ago. Let me know if you have problems on the
httpd side of things. I think some of the auth modules may
try to link against the DB libraries, so that may be an
issue. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> > and I'll take a look at what's involved in DB4 right now. :-)
>
> great, thanks a lot for all your help.
Here's (most of) a patch for the Berkeley upgrade. There's a bug in
it, as the configure step still fails to detect Berkeley 4.0, but I
think this is pretty close to what we'll need.
However, I just recalled that the whole reason we delayed this upgrade
in the first place is that there's a problem trying to use different
Berkeley versions between Apache and Subversion -- as I remember it,
mod_dav_svn was unable to load a different version of the Berkeley
shared libraries than the rest of httpd 2.0, so we can't upgrade until
Apache/APR does (?).
I think Mike Pilato and Greg Stein can comment more knowledgably about
this. In the meantime, here's the patch if you'd like to try and
figure out what I'm doing wrong. :-) It would be great if we could
have this ready so that when we finally _can_ upgrade, it's a
no-brainer.
-Karl
Upgrade to Berkeley DB 4.0.14.
This patch is unfinished. I think all the necessary code changes are
done, but something's still wrong with the configure step, as it does
not detect Berkeley 4.0 in /usr/local/BerkeleyDB.4.0 even when pass
the --with-berkeley-db flag.
* subversion/libsvn_fs/fs.c (cleanup_fs): Use fs->env->txn_checkpoint.
(svn_fs_close_fs): Use fs->env->txn_stat and fs->env->lock_stat, in
the instrumenting code.
* subversion/libsvn_fs/trail.c (begin_trail): Use
fs->env->txn_begin.
(abort_trail): Use fs->env->txn_abort.
(commit_trail): Use fs->env->txn_commit and fs->env->txn_checkpoint.
* INSTALL: Talk about Berkeley 4.0.14, not 3.3.11.
* ac-helpers/berkeley-db.m4 (SVN_LIB_BERKELEY_DB): Link to the .la
library unconditionally, as Berkeley now generates one. Make
workarounds look for Berkeley 4.0, not 3.3.
* configure.in (SVN_FS_WANT_DB_MAJOR, SVN_FS_WANT_DB_MINOR,
SVN_FS_WANT_DB_PATCH): Set to 4, 0, and 14 respectively.
Index: ./ac-helpers/berkeley-db.m4
===================================================================
--- ./ac-helpers/.svn/text-base/berkeley-db.m4.svn-base Mon Nov 19 15:28:02 2001
+++ ./ac-helpers/berkeley-db.m4 Wed Dec 26 17:20:44 2001
@@ -97,13 +97,7 @@
dbdir=`cd db/dist ; pwd`
SVN_DB_INCLUDES="-I$dbdir"
svn_lib_berkeley_db=yes
- # Linking directly to the .la is broken with --disable-shared
- # because Berkeley db does not seem to generate a .la library.
- if test "$enable_shared" = "yes"; then
- SVN_DB_LIBS="$dbdir/libdb-3.3.la"
- else
- SVN_DB_LIBS="-L$dbdir -ldb"
- fi
+ SVN_DB_LIBS="$dbdir/libdb-4.0.la"
elif test "$status" = "skip"; then
svn_lib_berkeley_db=no
else
@@ -115,9 +109,11 @@
# database library in /usr/local/lib, as libdb.a. There is no
# /usr/local/include/db.h. So if you check for /usr/local first, you'll
# get the old header file from /usr/include, and the new library from
- # /usr/local/lib --- disaster. Check for that bogosity first.
- places="std /usr/local/include/db3:/usr/local/lib /usr/local
- /usr/local/BerkeleyDB.$1.$2 /usr/include/db3:/usr/lib"
+ # /usr/local/lib. Disaster. We check for that bogosity first,
+ # and assume that the bogosity has carried over to the Berkeley
+ # 4.0.x series -- if it hasn't, someone please make a noise.
+ places="std /usr/local/include/db4:/usr/local/lib /usr/local
+ /usr/local/BerkeleyDB.$1.$2 /usr/include/db4:/usr/lib"
fi
# Now `places' is guaranteed to be a list of place specs we should
# search, no matter what flags the user passed.
Index: ./configure.in
===================================================================
--- ./.svn/text-base/configure.in.svn-base Fri Dec 21 11:05:35 2001
+++ ./configure.in Wed Dec 26 16:59:10 2001
@@ -116,9 +116,9 @@
# Build the filesystem library (and repository administration tool)
# only if we have an appropriate version of Berkeley DB.
-SVN_FS_WANT_DB_MAJOR=3
-SVN_FS_WANT_DB_MINOR=3
-SVN_FS_WANT_DB_PATCH=11
+SVN_FS_WANT_DB_MAJOR=4
+SVN_FS_WANT_DB_MINOR=0
+SVN_FS_WANT_DB_PATCH=14
SVN_LIB_BERKELEY_DB($SVN_FS_WANT_DB_MAJOR, $SVN_FS_WANT_DB_MINOR,
$SVN_FS_WANT_DB_PATCH)
Index: ./subversion/libsvn_fs/trail.c
===================================================================
--- ./subversion/libsvn_fs/.svn/text-base/trail.c.svn-base Mon Nov 19 15:27:58 2001
+++ ./subversion/libsvn_fs/trail.c Wed Dec 26 16:57:06 2001
@@ -52,7 +52,7 @@
trail->pool = svn_pool_create (pool);
trail->undo = 0;
SVN_ERR (DB_WRAP (fs, "beginning Berkeley DB transaction",
- txn_begin (fs->env, 0, &trail->db_txn, 0)));
+ fs->env->txn_begin (fs->env, 0, &trail->db_txn, 0)));
*trail_p = trail;
return SVN_NO_ERROR;
@@ -72,7 +72,7 @@
undo->func (undo->baton);
SVN_ERR (DB_WRAP (fs, "aborting Berkeley DB transaction",
- txn_abort (trail->db_txn)));
+ fs->env->txn_abort (trail->db_txn)));
svn_pool_destroy (trail->pool);
@@ -96,13 +96,13 @@
doesn't return DB_LOCK_DEADLOCK --- all deadlocks are reported
earlier. */
SVN_ERR (DB_WRAP (fs, "committing Berkeley DB transaction",
- txn_commit (trail->db_txn, 0)));
+ fs->env->txn_commit (trail->db_txn, 0)));
/* Do a checkpoint here, if enough has gone on.
The checkpoint parameters below are pretty arbitrary. Perhaps
there should be an svn_fs_berkeley_mumble function to set them. */
SVN_ERR (DB_WRAP (fs, "checkpointing after Berkeley DB transaction",
- txn_checkpoint (fs->env, 1024, 5, 0)));
+ fs->env->txn_checkpoint (fs->env, 1024, 5, 0)));
/* We don't destroy the pool; we assume it contains stuff which will
be useful beyond the transaction. */
Index: ./subversion/libsvn_fs/fs.c
===================================================================
--- ./subversion/libsvn_fs/.svn/text-base/fs.c.svn-base Tue Dec 18 11:51:20 2001
+++ ./subversion/libsvn_fs/fs.c Wed Dec 26 16:52:47 2001
@@ -132,12 +132,12 @@
/* Checkpoint any changes. */
{
- int db_err = txn_checkpoint (env, 0, 0, 0);
+ int db_err = env->txn_checkpoint (env, 0, 0, 0);
while (db_err == DB_INCOMPLETE)
{
apr_sleep (1000000L); /* microseconds, so 1000000L == 1 second */
- db_err = txn_checkpoint (env, 0, 0, 0);
+ db_err = env->txn_checkpoint (env, 0, 0, 0);
}
/* If the environment was not (properly) opened, then txn_checkpoint
@@ -269,8 +269,9 @@
int db_err;
/* Print transaction statistics for this DB env. */
- if ((db_err = txn_stat (fs->env, &t)) != 0)
- fprintf (stderr, "Error running txn_stat(): %s", db_strerror (db_err));
+ if ((db_err = fs->env->txn_stat (fs->env, &t, 0)) != 0)
+ fprintf (stderr, "Error running fs->env->txn_stat(): %s",
+ db_strerror (db_err));
else
{
printf ("*** DB txn stats, right before closing env:\n");
@@ -292,8 +293,9 @@
}
/* Print transaction statistics for this DB env. */
- if ((db_err = lock_stat (fs->env, &l)) != 0)
- fprintf (stderr, "Error running lock_stat(): %s", db_strerror (db_err));
+ if ((db_err = fs->env->lock_stat (fs->env, &l, 0)) != 0)
+ fprintf (stderr, "Error running fs->env->lock_stat(): %s",
+ db_strerror (db_err));
else
{
printf ("*** DB lock stats, right before closing env:\n");
Index: ./INSTALL
===================================================================
--- ./.svn/text-base/INSTALL.svn-base Thu Dec 20 16:34:19 2001
+++ ./INSTALL Wed Dec 26 17:06:11 2001
@@ -148,17 +148,17 @@
building a Subversion client that speaks to a remote (networked)
repository, you don't need it.
- You'll need Berkeley DB 3.3.11 installed on your system. You can
+ You'll need Berkeley DB 4.0.14 installed on your system. You can
get it from http://www.sleepycat.com/.
If you already have another version of Berkeley DB installed and
- don't want to downgrade, you can unpack the Berkeley 3.3.11
+ don't want to downgrade, you can unpack the Berkeley 4.0.14
distribution into a subdir named `db' in the top-level of the
Subversion source tree. Then Subversion will ignore the system
DB and use the one it found in its own source tree.
Alternatively, you can add this flag
- --with-berkeley-db=/usr/local/BerkeleyDB.3.3
+ --with-berkeley-db=/usr/local/BerkeleyDB.4.0
to your `configure' switches, and the build process will use the
named Berkeley. You may need to use a different path, of
@@ -354,11 +354,11 @@
this from happening, you have to tell Apache where to find the
version of db subversion uses. Right before configure:
- export LDFLAGS=-L/usr/local/BerkeleyDB.3.3/lib
- export CPPFLAGS=-I/usr/local/BerkeleyDB.3.3/include
+ export LDFLAGS=-L/usr/local/BerkeleyDB.4.0/lib
+ export CPPFLAGS=-I/usr/local/BerkeleyDB.4.0/include
- Add --with-dbm=db3 to the configure line. This note assumes
- you have installed Berkeley DB 3.3.11 at its default locations.
+ Add --with-dbm=db4 to the configure line. This note assumes
+ you have installed Berkeley DB 4.0.14 at its default locations.
For more info about the db requirement, see section III.C.1.
All instructions below assume you configured Apache to install
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Wed, Dec 26, 2001 at 02:34:33PM -0600, Karl Fogel wrote:
> Garrett Rooney <ro...@electricjellyfish.net> writes:
> > so as an asside, add my name to the list of people who are asking for
> > an upgrade to db4 ;-)
>
> s/ss/s,
i really need to learn how to spell/type... (no, i'm not sure if that
was a typo or a spelling error... probably a little of both)
> and I'll take a look at what's involved in DB4 right now. :-)
great, thanks a lot for all your help.
-garrett
--
garrett rooney Unix was not designed to stop you from
rooneg@electricjellyfish.net doing stupid things, because that would
http://electricjellyfish.net/ stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> so as an asside, add my name to the list of people who are asking for
> an upgrade to db4 ;-)
s/ss/s, and I'll take a look at what's involved in DB4 right now. :-)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Wed, Dec 26, 2001 at 02:03:20PM -0600, Karl Fogel wrote:
> Garrett Rooney <ro...@electricjellyfish.net> writes:
> > subversion required some changes to use neon 0.18.2, and those changes
> > are not in the most recent tarball. you will have to revert your
> > version of neon to 0.17.2
>
> Oh dear, this is a lot to ask though.
>
> I'll make a new tarball right now.
cool... i will update the port tonight. we do have another problem
though. apparently the db3-latest port, which we were using for
berkeley db, just got removed from the freebsd ports tree (with the
justification that db4 was now the latest, and that no ports were
relying on db3-latest (well, other than mine, which isn't in the tree
yet, so it doesn't count)).
as soon as subversion upgrades to db4, this won't be an issue at all,
but at the moment, even with a new tarball it will be a bit of a pain
to put together a fully functional port.
what i'll most likely do is roll a port that only builds ra_dav, since
the port is mostly useful for downloading a more recent subversion to
do development on, and if you're doing that, you don't really need
ra_local. once you've got a more recent svn, you can get an
appropriate bdb from outside the ports tree.
(i believe the db3 port itself isn't being upgraded to the more recent
db3 that we use because some ports will cease to work with a newer
db3... gotta love software that isn't really backwards compatable
within major versions...)
so as an asside, add my name to the list of people who are asking for
an upgrade to db4 ;-)
-garrett
--
garrett rooney Unix was not designed to stop you from
rooneg@electricjellyfish.net doing stupid things, because that would
http://electricjellyfish.net/ stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> subversion required some changes to use neon 0.18.2, and those changes
> are not in the most recent tarball. you will have to revert your
> version of neon to 0.17.2
Oh dear, this is a lot to ask though.
I'll make a new tarball right now.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Tue, Dec 25, 2001 at 11:22:20PM -0600, Florin Iucha wrote:
> On Tue, Dec 25, 2001 at 11:08:59PM -0600, Florin Iucha wrote:
> > Hello!
> >
> > The same happens with neon, but only during compilation (it somehow
> > passes the configure stage).
>
> Actually it doesn't:
> checking neon library version... checking for neon-config... /usr/local/bin/neon-config
> 0.18.2
> You have neon version 0.18.2,
> but Subversion needs neon 0.17.2.
> Please either install neon 0.17.2 on this system
>
> Hmmm, why isn't neon-0.18.2 good enough?
subversion required some changes to use neon 0.18.2, and those changes
are not in the most recent tarball. you will have to revert your
version of neon to 0.17.2
about the db3 issue, that is a problem with the configure script, and
it is worked around by my freebsd port of subversion (which has not
been committed yet due to a desire to wait until subversion hits beta,
so as to avoid getting a thousand bug reports about things we already
know about).
if you want to try the port, grab it at
http://electricjellyfish.net/subversion.tar.gz
(that will still require you to revert your neon port to the earlier
version. nothing that can be done about that until subversion
releases a new tarball, and i can upgrade the port.)
-garrett
--
garrett rooney Unix was not designed to stop you from
rooneg@electricjellyfish.net doing stupid things, because that would
http://electricjellyfish.net/ stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: compiling svn-588 on FreeBSD with stock neon and db3
Posted by Florin Iucha <fl...@iucha.net>.
On Tue, Dec 25, 2001 at 11:08:59PM -0600, Florin Iucha wrote:
> Hello!
>
> The same happens with neon, but only during compilation (it somehow
> passes the configure stage).
Actually it doesn't:
checking neon library version... checking for neon-config... /usr/local/bin/neon-config
0.18.2
You have neon version 0.18.2,
but Subversion needs neon 0.17.2.
Please either install neon 0.17.2 on this system
Hmmm, why isn't neon-0.18.2 good enough?
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4