public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kristov Atlas <author@anonymousbitcoinbook•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Compatibility Bitcoin-Qt with Tails
Date: Fri, 02 May 2014 13:46:37 -0400	[thread overview]
Message-ID: <5363D9FD.4070509@anonymousbitcoinbook.com> (raw)
In-Reply-To: <CA+s+GJC_1YzKNwQKSreWB73vZVMYmM=+CqonqP7XWcDFP7ZZLw@mail.gmail.com>


On 04/30/2014 03:02 AM, Wladimir wrote:
> On Sat, Apr 26, 2014 at 7:29 PM, Kristov Atlas
> <author@anonymousbitcoinbook•com> wrote:
>> Hey Wladimir,
>>
>> Thanks for building this binary. The initial problem with Qt was
>> resolved, and I was able to load the GUI that chooses my datadir. After
>> choosing the default datadir, however, it segfaulted.
> I've fixed the issue; at least on Debian 6 - which is a lot more
> conductive to development than tails :-). See
> https://github.com/bitcoin/bitcoin/pull/4094 for the gory details. New
> test build available:
>
> https://download.visucore.com/bitcoin/linux-gitian-3cbabfa.tar.gz
> (sigs: https://download.visucore.com/bitcoin/linux-gitian-3cbabfa.tar.gz.sig
> )
>
> Wladimir

Nice work! I can confirm that this dev binary runs smoothly in the 
latest version of Tails, v1.0. Screenshot proof here [1]. When this is 
incorporated into the next release of Bitcoin Core, will this make the 
usual Linux binary compatible, or will there be a special binary just 
for systems running the older Qt?

-Kristov

[1] http://postimg.org/image/p3ycwai9d/



  reply	other threads:[~2014-05-02 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 20:27 Wladimir
2014-04-26 17:29 ` Kristov Atlas
2014-04-27  6:52   ` Wladimir
2014-04-30  7:02   ` Wladimir
2014-05-02 17:46     ` Kristov Atlas [this message]
2014-05-02 18:28       ` Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5363D9FD.4070509@anonymousbitcoinbook.com \
    --to=author@anonymousbitcoinbook$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=laanwj@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox