Please test: Bitcoin v0.3.22 release candidate

[marcus_of_augustus]

Code:

$ ./bitcoin
./bitcoin: symbol lookup error: ./bitcoin: undefined symbol: gtk_widget_get_realized

Fedora 12

You'll have to build your own Fedora binaries.  bitcoin is built on a recent Ubuntu.

(this is one reason why I'm pushing to remove Linux binaries from our distribution entirely, leaving it up to packagers for each OS)

Ah, don't you mean I'll have to uninstall the repository OpenSLL package, download OpenSLL tar ball and rebuild OpenSSL with ECDSA and EC support and then I can build my own bitcoin binaries on Fedora?

Any dependencies to watch out for when putting my home-built OpenSLL into Fedora that you know of?

[xf2_org]

Ah, don't you mean I'll have to uninstall the repository OpenSLL package, download OpenSLL tar ball and rebuild OpenSSL with ECDSA and EC support and then I can build my own bitcoin binaries on Fedora?

Any dependencies to watch out for when putting my home-built OpenSLL into Fedora that you know of?

You don't have to uninstall any packages.  Just install bitcoin-custom openssl into /usr/local/openssl or somesuch.

[marcus_of_augustus]

Ah, don't you mean I'll have to uninstall the repository OpenSLL package, download OpenSLL tar ball and rebuild OpenSSL with ECDSA and EC support and then I can build my own bitcoin binaries on Fedora?

Any dependencies to watch out for when putting my home-built OpenSLL into Fedora that you know of?

You don't have to uninstall any packages.  Just install bitcoin-custom openssl into /usr/local/openssl or somesuch.

and what is the best way to redirect the linker away from the system openssl install to the bitcoin-custom openssl install when building bitcoind ?

[xf2_org]

Ah, don't you mean I'll have to uninstall the repository OpenSLL package, download OpenSLL tar ball and rebuild OpenSSL with ECDSA and EC support and then I can build my own bitcoin binaries on Fedora?

Any dependencies to watch out for when putting my home-built OpenSLL into Fedora that you know of?

You don't have to uninstall any packages.  Just install bitcoin-custom openssl into /usr/local/openssl or somesuch.

and what is the best way to redirect the linker away from the system openssl install to the bitcoin-custom openssl install when building bitcoind ?

Update the top of makefile.unix.  It is standard *nix build instructions... you must edit cflags/ldflags/etc.  Describing compiler and linker -I and -L is beyond the scope of this thread, though, I'm afraid.

[marcus_of_augustus]

Ah, don't you mean I'll have to uninstall the repository OpenSLL package, download OpenSLL tar ball and rebuild OpenSSL with ECDSA and EC support and then I can build my own bitcoin binaries on Fedora?

Any dependencies to watch out for when putting my home-built OpenSLL into Fedora that you know of?

You don't have to uninstall any packages.  Just install bitcoin-custom openssl into /usr/local/openssl or somesuch.

and what is the best way to redirect the linker away from the system openssl install to the bitcoin-custom openssl install when building bitcoind ?

Update the top of makefile.unix.  It is standard *nix build instructions... you must edit cflags/ldflags/etc.  Describing compiler and linker -I and -L is beyond the scope of this thread, though, I'm afraid.

I didn't ask you to. Just trying to establish some kind of standard way for people who (god forbid) prefer to build bitcoin on RH derivative linux.

It is the best chance for bitcoin to make it into those repositories and get wider adoption.

Anybody have plans to publish a makefile for building bitcoin on RH derivatives?

[marcus_of_augustus]

Code:

/usr/bin/ld: cannot find -lboost_thread

Fedora 12, boost-thread package is installed.

[xf2_org]

Code:

/usr/bin/ld: cannot find -lboost_thread

Fedora 12, boost-thread package is installed.

Add "-mt" suffix.

[liberty]

Ubuntu 64bit. the client RC3 works just fine.

[shackra]

i got this error when i try to compile the source:

Code:

jorge@Abril:~/Descargas/bitcoin/bitcoin-0.3.22rc3/src$ make -f makefile.unix 
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DUSE_UPNP=0 -I/usr/local/lib/wx/include/gtk2-unicode-static-2.9 -I/usr/local/include/wx-2.9 -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -pthread -DGUI -o obj/net.o net.cpp
/usr/include/miniupnpc/miniupnpc.h: In function ‘void ThreadMapPort2(void*)’:
/usr/include/miniupnpc/miniupnpc.h:53: error: too few arguments to function ‘UPNPDev* upnpDiscover(int, const char*, const char*, int, int, int*)’
net.cpp:980: error: at this point in file
/usr/include/miniupnpc/upnpcommands.h:117: error: too few arguments to function ‘int UPNP_AddPortMapping(const char*, const char*, const char*, const char*, const char*, const char*, const char*, const char*, const char*)’
net.cpp:994: error: at this point in file
make: *** [obj/net.o] Error 1
jorge@Abril:~/Descargas/bitcoin/bitcoin-0.3.22rc3/src$ 

my machine use Trisquel GNU/Linux 4.5 (Slaine) 64 bits

[lebish]

Downloading to test now!

[Matt Corallo]

Code:

/usr/include/miniupnpc/miniupnpc.h:53: error: too few arguments to function ‘UPNPDev* upnpDiscover(int, const char*, const char*, int, int, int*)’

This is an indication you used the wrong version of miniupnp.  You are looking for miniupnpc-1.5, not miniupnpc-1.5.DATE.

[humble]

Looking pretty good. The field that shows the balance could be a little wider. It's cutting off the last (right-most) digit of my balance. And it's not like I have that large of a balance ;-)

[BitcoinsWallet]

(...) Test feedback and additional translation updates requested. (...)

Tell me if Spanish translation or updates needed 

[Matt Corallo]

As a side note, if you wish to attempt to duplicate the builds, you can try using the script at https://gist.github.com/961527.
The Linux ones should end up with hash-identical binaries, but I've never tested the Win32 ones.  They might work, but I'd bet there are several small differences (build timestamps and such).
Please don't comment on the build system here, that is best left to another thread and/or direct questions on IRC (I'm BlueMatt). 

[marcus_of_augustus]

As a side note, if you wish to attempt to duplicate the builds, you can try using the script at https://gist.github.com/961527.
The Linux ones should end up with hash-identical binaries, but I've never tested the Win32 ones.  They might work, but I'd bet there are several small differences (build timestamps and such).
Please don't comment on the build system here, that is best left to another thread and/or direct questions on IRC (I'm BlueMatt). 

Got a link to a thread with Redhat derivative (Fedora, CentOS, RH) builds help.

It's just one missing package after another. The file "build-unix.txt" should perhaps be renamed "build-ubuntu.txt" ... not sure what other unix that file helps on but it is next to useless for RH.

[xf2_org]

Release candidate #4 source and binaries uploaded.

Changes:
- add chinese, esperanto translations
- update russian, italian translations
- OSX build tweaks
- Windows installer fixes

[AltPluzF4]

Hmm.
Windows 7 Pro x64
When I start my local miner, bitcoin.exe goes up to a constant 25% CPU usage (Quad Core) Even after closing phoenix, and bitcoin, the process remains (at 25% CPU) until I manually terminate it.

No issues with 0.3.21 though. Any ideas?

[Matt Corallo]

Hmm.
Windows 7 Pro x64
When I start my local miner, bitcoin.exe goes up to a constant 25% CPU usage (Quad Core) Even after closing phoenix, and bitcoin, the process remains (at 25% CPU) until I manually terminate it.

No issues with 0.3.21 though. Any ideas?

Might you inform us of which/how many threads are using so much cpu (using Process Explorer) as well as any other info you might deam worth sharing.

[shackra]

Code:

/usr/include/miniupnpc/miniupnpc.h:53: error: too few arguments to function ‘UPNPDev* upnpDiscover(int, const char*, const char*, int, int, int*)’

This is an indication you used the wrong version of miniupnp.  You are looking for miniupnpc-1.5, not miniupnpc-1.5.DATE.

huh, sorry :p
my baaad xD

[theboos]

Fedora 13 x64, bitcoin 3.22.rc3. Says "Generating" in bottom right corner and displays a meager hashrate in the left. Moreover, I can't turn it off since the option has been removed from the menu. Using up CPU, so not just a UI bug.