Any news on Bitcoin v0.9 release?

[Shahrukh]

Perhaps I missed it, but are there any messages showing up indicating an error when you go to make it?

He got stuck on make, however it is not throwing any error but theres not output of make commands

[1715251366]

1715251366

[1715251366]

1715251366

[1715251366]

1715251366

[1715251366]

1715251366

[cr1776]

Perhaps I missed it, but are there any messages showing up indicating an error when you go to make it?

He got stuck on make, however it is not throwing any error but theres not output of make commands

Maybe try verbose mode
V=1

Or
Debug:

make -d


I didn't try those just now though so ymmv.  :-)
But it might give some starting points

[Carlton Banks]

Perhaps I missed it, but are there any messages showing up indicating an error when you go to make it?

No, I scrapped the old build directory, then built again. I scrutinised the build output all the way from the start, no errors or warnings. All the commands appear to complete without complaint. And the target files do not build. No bitcoind or bitcoin-qt is produced after the compile. It's gotta be one of the compiler flags that the configure script names, I can't think what else.

I will try with the verbose output option, maybe there will be more useful detail


Edit - possibly an error:

"Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized."

[cr1776]

I presume you checked in the

~/bitcoin/src

directory to see if the new bitcoind was built in there?    (Just trying to cover all the bases).  :-)

(you might have to copy it to /usr/bin/  afterward if you want it globally accessible, but for testing purposes, probably not).

[Carlton Banks]

I presume you checked in the

~/bitcoin/src

directory to see if the new bitcoind was built in there?    (Just trying to cover all the bases).  :-)

(you might have to copy it to /usr/bin/  afterward if you want it globally accessible, but for testing purposes, probably not).

Yep, tried looking in there. Using verbose now, looks like it picks up the language to compile no troubles, so that's not it.

[Carlton Banks]

No errors or warnings.

The only conceivable clue is the final lines of the make output:

make[1]: Entering directory `/home/user/Documents/bitcoin-0.9.0rc1'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/user/Documents/bitcoin-0.9.0rc1'


There's an implication something got skipped.

[cr1776]

So, after the "executing depfiles commands" you get nothing?

You should see something like this after "config.status: executing depfiles commands" (I just went to rebuild it to see what I could tell):

Making all in src
make[1]: Entering directory `/home/user/bitcoin/src'
(CDPATH="${ZSH_VERSION+.}:" && cd .. && /bin/bash /home/user/bitcoin/src/build-aux/missing autoheader)
rm -f stamp-h1
touch bitcoin-config.h.in
cd .. && /bin/bash ./config.status src/bitcoin-config.h

...

This is the complete configure script output:

Code:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
checking for main in -ldb_cxx-4.8... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build bitcoind... yes
checking whether to build bitcoin-cli... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build Bitcoin Core GUI... yes (Qt4)
checking for operating system IPv6 support... yes
checking if ccache should be used... no
checking if wallet should be enabled... yes
checking whether to build with support for IPv6... yes
checking whether to build with support for UPnP... yes
checking whether to build with UPnP enabled by default... yes
checking whether to build GUI with support for D-Bus... yes
checking whether to build GUI with support for QR codes... yes
checking whether to build test_bitcoin-qt... yes
checking whether to build test_bitcoin... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/test/Makefile
config.status: creating src/qt/Makefile
config.status: creating src/qt/test/Makefile
config.status: creating share/setup.nsi
config.status: creating share/qt/Info.plist
config.status: creating qa/pull-tester/run-bitcoind-for-test.sh
config.status: creating qa/pull-tester/build-tests.sh
config.status: creating src/bitcoin-config.h
config.status: src/bitcoin-config.h is unchanged
config.status: executing depfiles commands

using Mint/Ubuntu 13.04 equivalent

[Carlton Banks]

So, after the "executing depfiles commands" you get nothing?

Oh no, it convincingly executes everything in the build script. With hundreds of output lines, no errors.

The three lines I posted two posts up are the very last three from those hundreds lines of error free make output.

[maaku]

Carlton Banks, nothing you've posted so far indicates an error. Those three lines are in fact telling you that it was successfully built. Try "make clean && make all" and pastebin the *entire* result.

[WayneManBat]

Carlton Banks, nothing you've posted so far indicates an error. Those three lines are in fact telling you that it was successfully built. Try "make clean && make all" and pastebin the *entire* result.

this is all i can come up with

[cr1776]

Carlton Banks, nothing you've posted so far indicates an error. Those three lines are in fact telling you that it was successfully built. Try "make clean && make all" and pastebin the *entire* result.

That would be my next suggestion or
make -f makefile.unix clean; make -f makefile.unix


Also, does

find / -name bitcoind

show it being built anywhere odd?


(I presume you did a too (assuming you just want bitcoind):
./configure --without-qt

)

[Carlton Banks]

Carlton Banks, nothing you've posted so far indicates an error. Those three lines are in fact telling you that it was successfully built. Try "make clean && make all" and pastebin the *entire* result.

That would be my next suggestion or
make -f makefile.unix clean; make -f makefile.unix


Also, does

find / -name bitcoind

show it being built anywhere odd?

Okay, in the /src directory is a 'Shared Library' called bitcoind and bitcoincli, so it actually is producing the targets. Sort of (also a bitcoin-qt 'Shared Library' in src/qt)

How can I make these ordinary executables, and not 'Shared Libraries'? bitcoin-qt only launches from the command line and I cannot use -connect to get the blockchain from my local 0.8 node (PaymentServer::ipcSendCommandLine : Payment request file does not exist:  "192.168.1.x")   < never mind....

Paste of make output: http://pastebin.com/mmtxsVK7

[cr1776]

Edited - based on your edit too (cut some).  ;-)

For example if I look at it from the CLI (this is built with the latest changes since rc1 so will be slightly different than your's), I see lots of stuff, including:
-rwxrwxr-x  1 user group  69750836 Feb 13 10:22 bitcoind
-rwxrwxr-x  1 user group  14246918 Feb 13 10:22 bitcoin-cli

If you are at the CLI, if you type this while in the src directory, it launches.  So I'm thinking this is just a GUI issue.


What do the properties show for the files?

[Carlton Banks]

Edited - based on your edit too (cut some).  ;-)

For example if I look at it from the CLI (this is built with the latest changes since rc1 so will be slightly different than your's), I see lots of stuff, including:
-rwxrwxr-x  1 user group  69750836 Feb 13 10:22 bitcoind
-rwxrwxr-x  1 user group  14246918 Feb 13 10:22 bitcoin-cli

If you are at the CLI, if you type this while in the src directory, it launches.  So I'm thinking this is just a GUI issue.


What do the properties show for the files?

GUI properties indicate that all 3 are executable, and the type is specified 'shared library (application/x-sharedlib)' for all 3. They are executable, but bitcoin-qt only works by launching it from the command prompt. Error if you try from the GUI: "Could not display "/home/username/Documents/bitcoin-0.9.0rc1/src/qt/bitcoin-qt - There is no application installed for shared library files.
Do you want to search for an application to open this file?". Sounds like it's trying to read the contents of the file, even though it's specified as executable.

Sorry, I've still got a little bit of a MS windows hangover, linux is still new to me really. The idea that a GUI bug or suchlike would cause this confusion didn't occur to me. I'm running it with Mate desktop on Mint 15, if that's useful. Perhaps Mate is known for being incapable of launching certain types of executables?

[cr1776]

Edited - based on your edit too (cut some).  ;-)

For example if I look at it from the CLI (this is built with the latest changes since rc1 so will be slightly different than your's), I see lots of stuff, including:
-rwxrwxr-x  1 user group  69750836 Feb 13 10:22 bitcoind
-rwxrwxr-x  1 user group  14246918 Feb 13 10:22 bitcoin-cli

If you are at the CLI, if you type this while in the src directory, it launches.  So I'm thinking this is just a GUI issue.


What do the properties show for the files?

GUI properties indicate that all 3 are executable, and the type is specified 'shared library (application/x-sharedlib)' for all 3. They are executable, but bitcoin-qt only works by launching it from the command prompt. Error if you try from the GUI: "Could not display "/home/username/Documents/bitcoin-0.9.0rc1/src/qt/bitcoin-qt - There is no application installed for shared library files.
Do you want to search for an application to open this file?". Sounds like it's trying to read the contents of the file, even though it's specified as executable.

Sorry, I've still got a little bit of a MS windows hangover, linux is still new to me really. The idea that a GUI bug or suchlike would cause this confusion didn't occur to me. I'm running it with Mate desktop on Mint 15, if that's useful. Perhaps Mate is known for being incapable of launching certain types of executables?

If you can run it from the CLI, it is definitely compiled and so would seem to be a GUI issue or typing (mime?) issue.   The bitcoind etc files in src, are definitely just "bitcoind" not "bitcoind.so" right?  :-)  (.so is usually shared object library).  

You might try a
make install

at the end if you haven't done that.  I am not sure under Mate, but perhaps it will fix the issue. Perhaps it is only looking for executable applications in certain directories (e.g. /usr/bin/ or /usr/local/bin) The good thing is that you got it installed without a problem, just not in Mate yet.  :-)

[madzooka]

So what's new in this version? I mean what's the main difference? What is improved?

[Carlton Banks]

So what's new in this version? I mean what's the main difference? What is improved?

The list for the current release candidate is here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes.md

[gmaxwell]

And is it 100% confirmed we'll be able to store up to 80 bytes of data in a transaction?  That would be a god-send for us.

No it's not guaranteed— recently we've been talking some about removing this, reducing this, and will likely make it switchable. So far the initial commentary we've seen mostly appears to be people looking to use it abusively and in ways which will be detrimental to the Bitcoin currency.

[Peter Todd]

It's been a while, and can't see anything on the Bitcoin Foundation's blog about it.  Any idea when it's getting released?  And is it 100% confirmed we'll be able to store up to 80 bytes of data in a transaction?  That would be a god-send for us.

You already can store data in transactions; OP_RETURN just makes it easier to do that in ways that harm the Bitcoin network less. For instance see Mastercoin's "class B" encoding: https://github.com/mastercoin-MSC/spec#class-b-transactions-also-known-as-the-multisig-method

My advice for new projects is to support multiple encoding methods, the same was Mastercoin did, so you aren't dependent on the Bitcoin devs. Incidentally there's no practical way to stop all those methods - even P2SH^2, itself a very invasive change to the ecosystem which is unlikely to happen, can't stop encoding data in P2SH scriptSigs without merkleized abstract syntax tree support and risky changes to the scripting language... and that in turn has the big risk that you make upgrades in the future, perhaps because a crypto algorithm has been weakened, much more difficult to implement.

Of course, that's why I'm spending my time working on actually improving fundamental scalability rather than wasting time trying to tell people what to do with a trust-free decentralized system...

[softtissue]

when does Bitcoin v0.9 release?