1 2016-03-18 00:58:31 <FakeSatoshi> Because BIP 142 Segwit Address can be discussed, can base64 encoding + 192bit hash be considered?
 2 2016-03-18 01:08:47 <FakeSatoshi> 2 Visually similiar symbols B 8  / S 5 would be reduced
 3 2016-03-18 01:13:33 <FakeSatoshi> And 8 new symbols from ascii added. (To get base64) suggested ones < > = _ ^ : . !
 4 2016-03-18 04:07:41 <frank1e> oh i see there is some new icon in the footer of bitcoin core now :)
 5 2016-03-18 04:07:50 <frank1e> just installed the latest version
 6 2016-03-18 15:14:21 <Chris_Stewart_5> wumpus: Is there an easy way to print to stdout or log information in test cases? I've tried something simple like cout << "Done"; but nothing shows up in my console
 7 2016-03-18 15:14:49 <wumpus> cout and printf should simply work
 8 2016-03-18 15:15:08 <wumpus> logging using LogPrintf will just get ignored
 9 2016-03-18 15:15:58 <wumpus> but there should be nothing catching standard output/error, as far as I know. Boost unit test also has some logging functions of itself, which can be enabled based on verbosity settings on the command line of environment, but I've never used them.
10 2016-03-18 15:25:17 <Chris_Stewart_5> Where is the test_bitcoin executable at any way? I ran ls . | grep test_bitcoin and all I got was
11 2016-03-18 15:25:30 <Chris_Stewart_5> test_bitcoin.cpp
12 2016-03-18 15:25:32 <Chris_Stewart_5> test_bitcoin.h
13 2016-03-18 15:25:44 <Chris_Stewart_5> even though I can still run the executable
14 2016-03-18 15:28:05 <wumpus> ls . | grep is kind of an interesting way to find something
15 2016-03-18 15:28:23 <wumpus> brush up on your unix commandline ninjitsu :-)
16 2016-03-18 15:28:32 <wumpus> e.g.: find . -name test_bitcoin
17 2016-03-18 15:36:14 <Chris_Stewart_5> I'll concede that I am a yellow belt when it comes to unix cl utilities but when I ran your command I got the same result
18 2016-03-18 15:36:59 <Chris_Stewart_5> however i can still run the command test_bitcoin - I wonder if it is on my $PATH some how
19 2016-03-18 15:37:10 <wumpus> if you can *run* the executable it should exist somewhere
20 2016-03-18 15:37:18 <wumpus> try `which test_bitcoin`
21 2016-03-18 15:37:29 <wumpus> yes, it's probably somewhere else as you expect
22 2016-03-18 15:37:40 <Chris_Stewart_5> yeah I can run it in ~ so it must be on my path
23 2016-03-18 15:38:00 <wumpus> it *should* be in src/test after a succeful build
24 2016-03-18 15:38:22 <Chris_Stewart_5> by successful build you mean a build of src/test right?
25 2016-03-18 15:38:41 <Chris_Stewart_5> by running make inside that dir
26 2016-03-18 15:38:48 <wumpus> doesn't matter, any build will also build src/test, unless you explicitly disbale buildling the tests...
27 2016-03-18 15:39:59 <Chris_Stewart_5> because when I run make inside of src/test and then ./test_bitcoin it says that the executable isn't found
28 2016-03-18 15:41:49 <wumpus> then your build is not succesful
29 2016-03-18 15:41:52 <wumpus> any errors?
30 2016-03-18 15:42:46 <Chris_Stewart_5> make -C .. bitcoin_test
31 2016-03-18 15:42:48 <Chris_Stewart_5> make[1]: Entering directory `/home/chris/dev/bitcoin/src'
32 2016-03-18 15:42:50 <Chris_Stewart_5> make[1]: *** No rule to make target `bitcoin_test'.  Stop.
33 2016-03-18 15:42:52 <Chris_Stewart_5> make[1]: Leaving directory `/home/chris/dev/bitcoin/src'
34 2016-03-18 15:42:54 <Chris_Stewart_5> make: *** [all] Error 2
35 2016-03-18 15:43:59 <wumpus> try just leaving out the options and typing 'make'
36 2016-03-18 15:44:43 <btcdrak> luke-jr: ping https://github.com/bitcoin/bips/pull/359 has been ACK'd. Once merged we can send a note to the bitcoin-dev list.
37 2016-03-18 15:45:45 <Chris_Stewart_5> chris@chris:~/.../src/test$ make
38 2016-03-18 15:45:47 <Chris_Stewart_5> make -C .. bitcoin_test
39 2016-03-18 15:45:49 <Chris_Stewart_5> make[1]: Entering directory `/home/chris/dev/bitcoin/src'
40 2016-03-18 15:45:51 <Chris_Stewart_5> make[1]: *** No rule to make target `bitcoin_test'.  Stop.
41 2016-03-18 15:45:53 <Chris_Stewart_5> make[1]: Leaving directory `/home/chris/dev/bitcoin/src'
42 2016-03-18 15:45:55 <Chris_Stewart_5> make: *** [all] Error 2
43 2016-03-18 15:45:57 <Chris_Stewart_5> do you want me to edit the Makefile?
44 2016-03-18 15:46:31 <wumpus> no
45 2016-03-18 15:46:42 <wumpus> you should never have to edit the makefile
46 2016-03-18 15:46:57 <wumpus> they are generated by configure (which is part of autoconf/automake)
47 2016-03-18 15:47:31 <Chris_Stewart_5> interesting
48 2016-03-18 15:47:43 <wumpus> CXX      test/test_test_bitcoin-rpc_tests.o
49 2016-03-18 15:47:43 <wumpus> $ make
50 2016-03-18 15:47:43 <wumpus> make[1]: Entering directory `/store/orion/projects/bitcoin/bitcoin/src'
51 2016-03-18 15:47:43 <wumpus> make -C .. bitcoin_test
52 2016-03-18 15:47:57 <wumpus> (and so on)
53 2016-03-18 15:47:57 <wumpus> that's my output, and I didn't have to do anything special
54 2016-03-18 15:48:14 <Chris_Stewart_5> hmmm... let me try and clone bitcoin in another dir to make sure I don't have something weird going on
55 2016-03-18 15:48:32 <wumpus> you did run ./autogen.sh first, then ./configure?
56 2016-03-18 15:48:48 <wumpus> and both succeeded without errors?
57 2016-03-18 15:49:19 <Chris_Stewart_5> No I don't think I ran those, they need to be run explicitly?
58 2016-03-18 15:49:41 <wumpus> yes, see build/build-unix.md for build instructions, that's definitely the first you should do
59 2016-03-18 15:49:44 <Chris_Stewart_5> I think I updated synced my master branch to the current master then tried to start running tests
60 2016-03-18 15:49:48 <wumpus> doc/build-unix.md
61 2016-03-18 15:50:03 <Chris_Stewart_5> Ok - I'll do that.
62 2016-03-18 15:50:20 <wumpus> but apparently you must have run them sometimes becasue you had a Makefile at all
63 2016-03-18 15:51:32 <Chris_Stewart_5> perhaps it was a left over from an older version? I just updated to master yesterday - I can't remember the last time I pulled before that
64 2016-03-18 15:52:11 <wumpus> probably, doesn't hurt running them again, although even then I don't understand the "make[1]: *** No rule to make target `bitcoin_test'.  Stop." error
65 2016-03-18 16:40:36 <Chris_Stewart_5> wumpus: You solved my issue I'm now getting information to stdout. I appreciate the help :-)
66 2016-03-18 19:20:08 <Luke-Jr> btcdrak: done
67 2016-03-18 23:18:39 <Chris_Stewart_5> wumpus: Is there an easy way to write a tx to stdout in hex format? cout << ???