[pybsddb] Published pybsddb3 4.7.0

Davies Liu davies.liu at gmail.com
Tue May 27 14:12:47 CEST 2008


On Tue, May 27, 2008 at 7:31 PM, Jesus Cea <jcea at argo.es> wrote:

> A near future pybsddb3 version will fully support the replication base
> API, so you will have full control of the replication process (and you
> will need to manage things like elections, sockets and such explicitly).
> At this level you don't need to use any special flag when compiling BDB,
> but the support code for replication work in your program, without
> Replication Manager support, will be far bigger and complex.
>


> | /temp.linux-x86_64-2.5/Modules/_bsddb.o
> | Modules/_bsddb.c:4658: error: expected identifier or '(' before '<<'
> token
> | Modules/_bsddb.c:4686: error: expected identifier or '(' before '=='
> token
> | Modules/_bsddb.c:6222: error: 'DBEnv_log_stat' undeclared here (not in a
>
> I guess you are merging bsddb3 code with "other" code using SVN , and
> you are having merging conflicts you are not resolving by hand...
>

Yes!


>
> Please, try again with a clear checkout (or, far better, use pypi
> released version) and with a previously compiled Berkeley DB with
> Replication Manager support.
>
> If you still have problems, let me know.
>
> PS: Unless explicitly stated, compiling BSDDB3 from SVN trunk is not
> garanteed to work, since the code is in a permanent state of flux.
>
> PPS: If providing a "--enable-pthread_api" flag to the configure step
> while compiling Berkeley DB solves you issue, I would suggest you to
> contact Gentoo guys to change BDB default compilation flags. Replication
> Manager should be compiled in, even if not used, to solve issues like
> yours...
>

I install bdb 4.6.21 with default configuration at
/usr/local/BerkeleyDB-4.6.21,
without --enable-pthread_api, then build bsddb3 with
--berkeley-db=/usr/local/BerkeleyDB-4.6.21,
it works.

Thank you !

-- 
Best regards,

Davies Liu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jcea.es/pipermail/pybsddb/attachments/20080527/96b4832e/attachment.htm>


More information about the pybsddb mailing list