*** ALERT *** Upgrade to 0.3.6 ASAP!
Please upgrade to 0.3.6 ASAP! We fixed an implementation bug where it was possible that bogus transactions could be displayed as accepted. Do not accept Bitcoin transactions as payment until you upgrade to version 0.3.6!
If you can’t upgrade to 0.3.6 right away, it’s best to shut down your Bitcoin node until you do.
Also in 0.3.6, faster hashing:
- midstate cache optimisation thanks to tcatm
- Crypto++ ASM SHA-256 thanks to BlackEye Total generating speedup 2.4x faster.
Download: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.6/
Windows and Linux users: if you got 0.3.5 you still need to upgrade to 0.3.6.
Please upgrade to 0.3.6 ASAP! We fixed an implementation bug where it was possible that bogus transactions could be displayed as accepted. Do not accept Bitcoin transactions as payment until you upgrade to version 0.3.6!
If you can’t upgrade to 0.3.6 right away, it’s best to shut down your Bitcoin node until you do.
Also in 0.3.6, faster hashing:
- midstate cache optimisation thanks to tcatm
- Crypto++ ASM SHA-256 thanks to BlackEye Total generating speedup 2.4x faster.
Download: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.6/
Windows and Linux users: if you got 0.3.5 you still need to upgrade to 0.3.6.
With the official Linux-64bit build, run on Fedora 13, I see it failing badly:
Code:************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in AppInit()
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in CMyApp::OnUnhandledException()
terminate called after throwing an instance of ‘DbRunRecoveryException’ what(): DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
Praying my bitcoins aren’t eaten…
Quote from: jgarzik on July 29, 2010, 07:42:15 PM
With the official Linux-64bit build, run on Fedora 13, I see it failing badly:
Code:************************ EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in AppInit()
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in CMyApp::OnUnhandledException()terminate called after throwing an instance of ‘DbRunRecoveryException’ what(): DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
Praying my bitcoins aren’t eaten…
I think you’ll be ok, it blew up on me too. Run the older version, you should still see all your coins. Backup first for the next Linux release Wink
Quote from: jgarzik on July 29, 2010, 07:42:15 PM
With the official Linux-64bit build, run on Fedora 13, I see it failing badly:
Same result on another machine. BDB errors, and death. 0.3.5 on 64bit Linux is questionable. You didn’t mix up the builds with 32-bit Linux, did you?
debug.log says: Code:Bitcoin version 0.3.5 beta Default data directory /g/g/.bitcoin Bound to port 8333 Loading addresses… dbenv.open strLogDir=/garz/bitcoin/data/database strErrorFile=/garz/bitcoin/data/db.log
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in AppInit()
Quote from: knightmb on July 29, 2010, 07:47:37 PM
I think you’ll be ok, it blew up on me too. Run the older version, you should still see all your coins. Backup first for the next Linux release
Double-ACK Smiley
older version (SVN 117 + listtransactions + getinfo KHPS) works fine, all bitcoins there. And yes, I should back up before following “please upgrade” instructions… Smiley
[Deleted] Quote from: davidonpda on July 29, 2010, 07:51:38 PM
Can windows users upgrade to the 3.5 for now?
Yes, I’ve tested on Windows XP, 2003, and 7 all went through just fine. You’ll enjoy the speed increase as well. Wink
[err, wait I guess, new version about to spawn]
Haven’t had time to update the SVN yet. Wait for 0.3.6, I’m building it now. You can shut down your node in the meantime.
SVN is updated with version 0.3.6.
Uploading Windows build of 0.3.6 to Sourceforge now, then will rebuild linux.
Ha! One of the changes in there is updated some v “0.3.3” stuff to “0.3.6” but that isn’t the important part of the update. :-)
SVN r119 seems to work fine here. No BDB explosion.
Tested the Windows build across XP, 2003, Vista, 7 (both 32 and 64bit builds), no issues installing or running client. So far so good, looking forward to the Linux client. Wink
0.3.6 Linux build is back to the old makefile.unix. It static links libjpeg so that shouldn’t be a problem.
Is that working better?
If you got 22DbRunRecoveryException and you’ve used someone else’s build before, you may need to delete (or move the files somewhere else) database/log.000000*
Windows and Linux users: if you got 0.3.5 you still need to upgrade to 0.3.6.
0.3.6 binaries for linux works fine on two my machines (64 and 32 bits) with Debian squeeze/sid
Quote from: bitcoinex on July 29, 2010, 09:27:15 PM
0.3.6 binaries for linux works fine on two my machines (64 and 32 bits)
If you (and others) are willing, please post your OS + OS version, when posting success/failure reports.
I will echo a recommendation to satoshi from another forum member: build linux binaries on an older Linux OS, to ensure wider compatibility. Maybe something as old as CentOS 5 (caveat: requires custom openssl, boost, db4 and wx builds).
Ah, mine is linked to 2.10.1, I’ll bring my system up to bleeding edge to see if that solves it Grin
[edit] Well turns out I can’t package wise as they top out at 2.10 for now
Quote from: jgarzik on July 29, 2010, 09:30:08 PM
Quote from: bitcoinex on July 29, 2010, 09:27:15 PM
0.3.6 binaries for linux works fine on two my machines (64 and 32 bits)
If you (and others) are willing, please post your OS + OS version, when posting success/failure reports.
I will echo a recommendation to satoshi from another forum member: build linux binaries on an older Linux OS, to ensure wider compatibility. Maybe something as old as CentOS 5 (caveat: requires custom openssl, boost, db4 and wx builds).
I would agree, would help those of us not on the bleeding edge of distro packages. Smiley
Quote from: jgarzik on July 29, 2010, 09:30:08 PM
Quote from: bitcoinex on July 29, 2010, 09:27:15 PM
0.3.6 binaries for linux works fine on two my machines (64 and 32 bits)
If you (and others) are willing, please post your OS + OS version, when posting success/failure reports.
I will echo a recommendation to satoshi from another forum member: build linux binaries on an older Linux OS, to ensure wider compatibility. Maybe something as old as CentOS 5 (caveat: requires custom openssl, boost, db4 and wx builds).
sorry. I’m checked binaries on Debian GNU/Linux squeeze/sid
”./bitcoin: /lib64/libc.so.6: version `GLIBC_2.11’ not found (required by ./bitcoin)” isn’t a new problem that started with 0.3.6 is it? This was built on the same OS installations as 0.3.0.
Unfortunately I upgraded to Ubuntu 10.04 before 0.3.0. I will not upgrade anymore. I don’t know when I might have time to reinstall to downgrade, but at least by not upgrading, it’ll gradually fix itself.
Ubuntu Linux 9.10
Error:
/lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.11’ not found Cry
On Debian testing 32-bit, I get a few build errors, all resembling: Code:script.cpp:114: error: �OP_NOP1� was not declared in this scopeI got these when attempting to “make bitcoind” without “make clean” or “make” first. It looks like the bitcoind build instructions don’t compile the headers first, but they also don’t delete the headers.h.gch, so the old headers are used if present.
If anyone else gets this error, the simplest solution is to “make clean” and retry the build.
Quote from: satoshi on July 29, 2010, 09:43:15 PM
”./bitcoin: /lib64/libc.so.6: version `GLIBC_2.11’ not found (required by ./bitcoin)” isn’t a new problem that started with 0.3.6 is it? This was built on the same OS installations as 0.3.0.
Unfortunately I upgraded to Ubuntu 10.04 before 0.3.0. I will not upgrade anymore. I don’t know when I might have time to reinstall to downgrade, but at least by not upgrading, it’ll gradually fix itself.
That’s strange, 0.3.3 worked fine on it. It’s no biggie, I need to upgrade that machine anyway.
Quote from: WMFrend on July 29, 2010, 10:08:14 PM
Ubuntu Linux 9.10
Error:
/lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.11’ not found
dpkg -l | egrep "(libc6|glibc)"
# This will display what version you currently have installed
# I guess you have glibc version 2.10 or older installed.
apt-get update
apt-cache showpkg libc6 | less
# Look (near the bottom) for the versions available for a 2.11 version
#Maybe you can just upgrade with:
apt-get upgrade libc6
# Above instruction for a real debian system, they might work with UbuntuQuote from: lachesis on July 29, 2010, 10:14:36 PM
On Debian testing 32-bit, I get a few build errors, all resembling:
Code:script.cpp:114: error: OP_NOP1 was not declared in this scopeI got these when attempting to “make bitcoind” without “make clean” or “make” first. It looks like the bitcoind build instructions don’t compile the headers first, but they also don’t delete the headers.h.gch, so the old headers are used if present.
If anyone else gets this error, the simplest solution is to “make clean” and retry the build. We don’t really need pre-compiled header. It only makes it compile slightly faster. I think I’ll just get rid of it. Even still, you’d still need to remember to “make -f makefile.unix clean” or delete headers.h.gch one more time to get rid of the leftover file.
Damn that GLIBC_2.11. I thought I’d been careful not to accept any of the updates.
would an auto-update function built into bc be possible?
Quote from: andy_3_913 on July 30, 2010, 04:04:51 PM
would an auto-update function built into bc be possible?
It’s something that I have already suggested here :| http://bitcointalk.org/index.php?topic=259.0
Quote from: Joozero on July 30, 2010, 04:49:25 PM
Quote from: andy_3_913 on July 30, 2010, 04:04:51 PM
would an auto-update function built into bc be possible?
It’s something that I have already suggested here :| http://bitcointalk.org/index.php?topic=259.0
sorry! Smiley
I can only imagine the pain you went through to get these builds because I’m trying to build the program on a Ubuntu 9.04 box and so far I can’t seem to find all the dependencies to compile no matter how much I keep installing packages and compiling source, LOL.
Quote from: knightmb on July 30, 2010, 07:24:07 PM
I can only imagine the pain you went through to get these builds because I’m trying to build the program on a Ubuntu 9.04 box and so far I can’t seem to find all the dependencies to compile no matter how much I keep installing packages and compiling source, LOL.
I can’t understand why you’re having so much pain. I just followed the instructions in build-unix.txt. I made a couple little corrections for Boost 1.37, which I’ll put on SVN the next time I update it, noted below:
Dependencies
------------
sudo apt-get install build-essential
sudo apt-get install libgtk2.0-dev
sudo apt-get install libssl-dev
sudo apt-get install libdb4.7-dev
sudo apt-get install libdb4.7++-dev
sudo apt-get install libboost-all-dev (or libboost1.37-dev)
wxWidgets
---------
cd /usr/local
tar -xzvf wxWidgets-2.9.0.tar.gz
cd /usr/local/wxWidgets-2.9.0
mkdir buildgtk
cd buildgtk
../configure --with-gtk --enable-debug --disable-shared --enable-monolithic
make
sudo su
make install
ldconfigadded a comment in makefile.unix:
# for boost 1.37, add -mt to the boost libraries
LIBS= \<br>
-Wl,-Bstatic \<br>
-l boost_system \<br>
-l boost_filesystem \<br>
-l boost_program_options \<br>
-l boost_thread \<br>
-l db_cxx \<br>
-l crypto \<br>
-Wl,-Bdynamic \<br>
-l gthread-2.0Quote from: satoshi on July 30, 2010, 07:53:06 PM
I can’t understand why you’re having so much pain. I just followed the instructions in build-unix.txt. I made a couple little corrections for Boost 1.37, which I’ll put on SVN the next time I update it, noted below:
Dependencies
sudo apt-get install build-essential sudo apt-get install libgtk2.0-dev sudo apt-get install libssl-dev sudo apt-get install libdb4.7-dev sudo apt-get install libdb4.7++-dev sudo apt-get install libboost-all-dev (or libboost1.37-dev)
That part I highlighted is what got me. You can’t install all the libboost packages with that command (I tried to cheat with a * also), but part of my issue is I took it too literal like install everything that had to do with libboost, LOL.
Really, all that was needed was the libboost1.37-dev package and that made all the compile errors go away. Everything else worked out just fine as far as compiling your own wxWidgets, compiling Boost 1.4, etc.
So that last command should simply be sudo apt-get install libboost1.37-dev
On a side note, I compiled mine on a Ubuntu 64bit system, so the finished program came out 64bit aware. I’m testing it out on some 64bit systems to see how well things go.
Quote from: knightmb on July 30, 2010, 08:04:19 PM
So that last command should simply be
sudo apt-get install libboost1.37-dev Except that wouldn’t work for boost 1.40+ (on Ubuntu 10.04), where you need to get libboost-all-dev.
Seems they changed everything around in Boost recently, “-mt” and all that, makes it hard.
BTW, I tried Boost 1.34 but it didn’t have the boost.interprocess stuff.
Mac OSX version is available now. See bitcoin.org or the SourceForge link.