I'm not focusing on that bug, I addressed it because someone else brought it up. If I was going to bitch constantly about one thing, it would be NOT FUCKING COMPILING ON LINUX. 
Okay I missed that one (it does compiler for me on Ubuntu). Can you be more specific?
Give me just a minute. I'll attempt to compile it yet again and then post the results.
Here you are. I copied the whole thing, not just the relevant bits, in case I would have missed something: http://pastebin.com/Nc5XrpEH
Wow. Just... wow. I did a "make clean", then tried "make build-debug" just for fun... I think the devs failed so hard they won: http://pastebin.com/c9X2H7a9
Anyone have a solution for the above?
Did you try gcc 4.8.x as suggested?
Did you even look at the first pastebin? You might be able to blame the compiler for the debug build failure, but saying a compiler bug is responsible for the regular build failure is ludicrous.
Whether or not its a problem with the compiler has to be eliminated. If you refuse to eliminate it as a factor then we will end up with the same discussion over and over; that is the ludicrous part. Come back when you're ready to fix your problem, otherwise just deal with it yourself.
Okay, your faucet is broken. So the obvious thing to do is get the engine in your car checked; anything else is ludicrous. You're asking me to hunt down an old ass package or custom compile an old version of GCC - while the obvious problem is "shit ain't being linked correctly."
Either you know jack shit about C/C++ and coding in general, or you like wasting people's time.
Such is life, either do something about it or just whine until the your mouth froths with saliva. I'm sure you find the latter more worthwhile. Cheers.
Sorry all, this is fixed now, thank eizh for corrections.
). A separate public key is generated for each input and they're difficult to link by blockchain analysis.
