Quote from: nostromo429 on December 08, 2013, 06:36:08 PM

I'm running into this problem with bitcoind and BerkeleyDB on Debian wheezy myself, now, in a brand-new installation from scratch.

Question: What does the

Code:

--with-incompatible-bdb

"fix" actually cause to happen? Namely, that copies of the wallet from this instance couldn't be used with other bitcoin installations? That's bad.

I'm curious why BDB 4.8 is still being used, it seems to be near obsolescence even on known-glacial distros (CentOS and Debian stable).

My problem is that IFF

Code:

--with-incompatible-bdb

does break moving wallets between clients, I can't use it. It's a hard requirement. Debian 7 is also a hard requirement.

Options? Maybe I could build BDB 4.8 and shove it someplace really out-of-the-way like /opt?

Thanks in advance!

you can always export the privkeys and import them on the other instance if they're really incompatible. Anyways, if you are building both servers you probably will use the same version and then they will be compatible between them.

Adriano