1 2016-11-19 00:04:17	0|cfields|clang?
 2 2016-11-19 00:11:15	0|BlueMatt|jtimon: hmm? I havent made it....since its likely to conflict like hell with everything I figure I should probably prep it when everything else is reviewed and in
 3 2016-11-19 00:11:19	0|BlueMatt|instead of rebasing constantly
 4 2016-11-19 00:13:54	0|Lightsword|cfields, does the default clang on debian 7 support c++11?
 5 2016-11-19 00:15:22	0|Lightsword|hmm, would appear debian 7 is default version 3.0 and min is 3.3 for c++11
 6 2016-11-19 00:26:33	0|jtimon|BlueMatt: ok
 7 2016-11-19 00:27:41	0|BlueMatt|jtimon: it should be +/- the same as the branch I gave you about a month ago
 8 2016-11-19 00:27:50	0|BlueMatt|I think the current prs are all still that branch rebased without any major changes
 9 2016-11-19 00:28:11	0|jtimon|BlueMatt: yeah was just curious on your plans about it
10 2016-11-19 00:53:25	0|sipa|Lightsword: that's annoying...
11 2016-11-19 00:53:37	0|sipa|Lightsword: you could compile a static binary on a later system
12 2016-11-19 00:54:20	0|Lightsword|sipa, yeah that’s what I recommended
13 2016-11-19 00:58:55	0|cfields|the release binaries should be fine for that unless it needs patching
14 2016-11-19 03:30:28	0|BlueMatt|cfields: hey
15 2016-11-19 03:31:02	0|BlueMatt|cfields/sipa: sorry, been missing all day, happy to chat about CConnman design if y'all're free, or can wait till tomorrow
16 2016-11-19 05:06:24	0|phantomcircuit|anybody have an opinion on where fuzzing examples should go? (ie which directory)
17 2016-11-19 05:06:33	0|phantomcircuit|i was thinking contrib
18 2016-11-19 05:07:44	0|luke-jr|phantomcircuit: under qa/?
19 2016-11-19 05:08:12	0|BlueMatt|luke-jr: only if there is infrastructure to automatically run them (travis, or if its too slow, at least some scripts)
20 2016-11-19 05:08:13	0|BlueMatt|but, yes
21 2016-11-19 05:08:39	0|phantomcircuit|luke-jr, yeah that sounds better
22 2016-11-19 05:56:51	0|meownow|can anyone summarize when i download the bitcoin source code on the github, what is the client i am downloading able to actually do?
23 2016-11-19 05:58:44	0|achow101|meownow: it fully verifies all blocks and transactions, relays said blocks and transactions, can manage a wallet, does signing operations with ecdsa keys, produces block template for miners
24 2016-11-19 06:02:55	0|meownow|ok thanks. so with it i can donate my cpu to acting as a node to store and verify blocks and transactions, which other nodes will very their own blocks against? as well as the other things you mentioned i can do.
25 2016-11-19 06:07:18	0|achow101|no, nothing is verified against someone else. your node has a set of hard coded rules and it will verify blocks and transactions according to those rules. every other node will do the same, verify the block against the built-in rules
26 2016-11-19 10:32:41	0|gmaxwell|Oh good, I was worrying that my C++ compile times were getting too fast  https://github.com/kw-udon/constexpr-8cc
27 2016-11-19 15:16:16	0|bitcoin-git|[13bitcoin] 15laanwj opened pull request #9190: qt: Plug many memory leaks (06master...062016_11_plug_leaks) 02https://github.com/bitcoin/bitcoin/pull/9190
28 2016-11-19 15:19:08	0|bitcoin-git|13bitcoin/06master 1412519bf 15Wladimir J. van der Laan: test: Fix use-after-free in scheduler tests...
29 2016-11-19 15:19:08	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/9346f8429957...ce612f175063
30 2016-11-19 15:19:09	0|bitcoin-git|13bitcoin/06master 14ce612f1 15Wladimir J. van der Laan: Merge #9186: test: Fix use-after-free in scheduler tests...
31 2016-11-19 15:19:23	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #9186: test: Fix use-after-free in scheduler tests (06master...062016_11_scheduler_fix) 02https://github.com/bitcoin/bitcoin/pull/9186
32 2016-11-19 19:04:36	0|meownow|im currently reading through the first commit of the bitcoin source code onto github. seems a good way to familiarize myself with the core of the code base and what it does.
33 2016-11-19 19:27:19	0|instagibbs|meownow reading code that relates to specific issues or pull requests helps me the most
34 2016-11-19 20:01:48	0|luke-jr|instagibbs: he left.
35 2016-11-19 20:02:25	0|luke-jr|but in case he reads the log: I don't recommend reading the earliest code as a way to learn about Bitcoin. It was a mess, and included a lot of features later discarded (eg, built-in marketplace)
36 2016-11-19 20:08:19	0|gmaxwell|I don't agree it was a mess. it was also quite short, there were some irrelevant parts to skip over... sure.. but it's much easier to read than the current codebase if for no other reason than size.
37 2016-11-19 20:09:06	0|sipa|it's probably a relatively good way to understand the design of bitcoin, but it's not that helpful to learn how the code works now
38 2016-11-19 20:13:39	0|BlueMatt|hmmm....whens the last time anyone built with lto?
39 2016-11-19 20:14:37	0|sipa|BlueMatt: i did a few months ago
40 2016-11-19 20:16:17	0|luke-jr|gmaxwell: well, it certainly wasn't as modular/abstracted as it is now
41 2016-11-19 20:16:34	0|BlueMatt|sipa: what did you have to do it?
42 2016-11-19 20:16:50	0|luke-jr|unless things got significantly worse by 0.3.19 which is probably the oldest I've actually looked over much
43 2016-11-19 20:17:02	0|sipa|BlueMatt: it was hard :)
44 2016-11-19 20:17:22	0|BlueMatt|oh :(
45 2016-11-19 20:17:41	0|BlueMatt|still have patches?
46 2016-11-19 20:17:44	0|luke-jr|O.o
47 2016-11-19 20:17:57	0|sipa|no patches, just a long ./configure line
48 2016-11-19 20:18:10	0|BlueMatt|still have it in .bash_history? :p
49 2016-11-19 20:18:20	0|sipa|nope
50 2016-11-19 20:18:43	0|luke-jr|I would think you'd just need to build/link everything with -flto? no?
51 2016-11-19 20:18:47	0|luke-jr|(including system libs..)
52 2016-11-19 20:18:55	0|BlueMatt|sipa: did you have to set ar=gcc-ar, etc?
53 2016-11-19 20:19:02	0|BlueMatt|luke-jr: lolno that dont work
54 2016-11-19 20:19:25	0|sipa|luke-jr: if you do everything through gcc, it will work
55 2016-11-19 20:19:33	0|sipa|but not if you invoke ld, ar, ... directly
56 2016-11-19 20:19:57	0|sipa|BlueMatt: i remember that it needed absolute paths for those tools
57 2016-11-19 20:20:06	0|sipa|and that it took me hours to figure that out
58 2016-11-19 20:20:09	0|sipa|or something like that
59 2016-11-19 20:21:04	0|luke-jr|as long ago as 2012, this user got his system including KDE all LTO'd: http://realnc.blogspot.com/2012/06/building-gentoo-linux-with-gcc-47-and.html :p
60 2016-11-19 20:21:38	0|BlueMatt|sipa: see? you already saved me a bunch of time :)
61 2016-11-19 20:22:38	0|luke-jr|that -fno-linker-plugin might be related to that
62 2016-11-19 20:25:27	0|sipa|BlueMatt: i think this works:
63 2016-11-19 20:25:39	0|sipa|./configure AR=/usr/bin/gcc-ar NM=/usr/bin/gcc-nm RANLIB=/usr/bin/gcc-ranlib CPPFLAGS="-O2 -flto" CFLAGS="-O2 -flto" LDFLAGS="-flto" --with-incompatible-bdb
64 2016-11-19 20:26:53	0|sipa|or CXXFLAGS maybe
65 2016-11-19 20:27:58	0|BlueMatt|sipa: nope, still getting the same shit i was previously: undefined reference to boost::filesystem::path::~path()
66 2016-11-19 20:28:04	0|BlueMatt|(which is implicitly defined, i checked)
67 2016-11-19 20:28:28	0|BlueMatt|via bitcoin_util.a
68 2016-11-19 20:31:19	0|sipa|BlueMatt: worked for me (gcc 6.2.0)
69 2016-11-19 20:31:58	0|BlueMatt|6.2.1 here w boost 1.62
70 2016-11-19 20:32:10	0|sipa|and boost 1.54
71 2016-11-19 20:33:15	0|luke-jr|what distro is using GCC 6 already? :o
72 2016-11-19 20:35:20	0|gmaxwell|luke-jr: fedora, arch, debian testing?
73 2016-11-19 20:36:46	0|luke-jr|hmm, does that mean all of Debian compiles with it? or do they have older compilers used for some pkgs?
74 2016-11-19 20:37:27	0|luke-jr|sorry, kinda off-topic, I'll just google
75 2016-11-19 20:37:36	0|gmaxwell|I dunno about debian, but when fedora releases with a new gcc, all of fedora compiles with it (potentially carrying patches to both GCC and a few packages).
76 2016-11-19 20:38:47	0|luke-jr|just surprised considering Gentoo stable is still on GCC 4
77 2016-11-19 20:39:14	0|sipa|luke-jr: ubuntu 16.10
78 2016-11-19 20:39:19	0|sipa|has gcc 6
79 2016-11-19 20:39:48	0|sipa|i don't know whether they use that for release binaries, though
80 2016-11-19 20:39:53	0|gmaxwell|netcraft confirms, gentoo dying.
81 2016-11-19 20:40:11	0|sipa|netcraft confirms: netcraft dying
82 2016-11-19 20:40:33	0|luke-jr|lol
83 2016-11-19 20:40:57	0|luke-jr|well, at least it seems there are real blockers to GCC 6: https://bugs.gentoo.org/show_bug.cgi?id=582084
84 2016-11-19 20:42:11	0|sipa|gcc6 by default compiles with c++14
85 2016-11-19 20:42:27	0|sipa|perhaps some packages don't explicitly set the c++ version?
86 2016-11-19 20:44:04	0|luke-jr|could be
87 2016-11-19 20:44:33	0|BlueMatt|luke-jr: a brief glance at some of those bugs indicates that they're just sitting idle with no desire to merge dead simple patches
88 2016-11-19 20:44:40	0|BlueMatt|indeed, gentoo is dying
89 2016-11-19 22:24:11	0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #9191: [qa] 0.13.2 Backports (060.13...06Mf1611-q01302) 02https://github.com/bitcoin/bitcoin/pull/9191
90 2016-11-19 22:34:17	0|bitcoin-git|13bitcoin/06master 14dfa44d1 15Russell Yanofsky: [qa] Wait for specific block announcement in p2p-compactblocks...
91 2016-11-19 22:34:17	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/ce612f175063...44adf683ad23
92 2016-11-19 22:34:18	0|bitcoin-git|13bitcoin/06master 1444adf68 15MarcoFalke: Merge #9159: [qa] Wait for specific block announcement in p2p-compactblocks...
93 2016-11-19 22:34:32	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #9159: [qa] Wait for specific block announcement in p2p-compactblocks (06master...06cmpct-announce-wait) 02https://github.com/bitcoin/bitcoin/pull/9159