public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kristov Atlas <kristovatlas@gmail.com>
To: "Warren Togami Jr." <wtogami@gmail.com>,
	 Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Wed, 23 Apr 2014 16:52:31 -0400	[thread overview]
Message-ID: <5358280F.2050108@gmail.com> (raw)
In-Reply-To: <CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

On 04/23/2014 04:39 PM, Warren Togami Jr. wrote:
> On Wed, Apr 23, 2014 at 10:05 AM, Kristov Atlas 
> <kristovatlas@gmail.com <mailto:kristovatlas@gmail.com>> wrote:
>
>     I see that the latest nightly build (thanks for that, Warren) is
>     still not compatible with Tails/Debian Squeeze. Is there still an
>     intention to address this issue? Might it be fixed by 0.9.2?
>
>
> If I understand the situation, bitcoind does work but not bitcoin-qt 
> due to qt-4.6?  If that is so, then the official Bitcoin 0.8.6 
> binaries didn't work on Squeeze either this is not a regression.
>
> The priority is for bitcoind to work on as many distributions as 
> reasonably possible as older stable distributions are most often 
> headless.  If you are a rare user who needs Bitcoin-Qt on an 
> incompatible system you can at least build it from source.
>
> Warren

Bitcoin-Qt 0.8.6 worked fine on Tails (and Debian Squeeze, I assume). 
So, it is a regression.

Here's output from the latest nightly build for Linux:

amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$ ./bitcoin-qt
./bitcoin-qt: symbol lookup error: ./bitcoin-qt: undefined symbol: _ZN19QAbstractProxyModel11setItemDataERK11QModelIndexRK4QMapIi8QVariantE

Since Tails has many simple development tools like "make" stripped out 
for security reasons, one could not simply build from source in Tails. 
It might be possible to build in Debian Squeeze and transplant that, 
however. I'll have to give that a shot some time. I'd argue that Tails 
is an incredibly important -- and hardly obscure -- Linux distribution 
that Bitcoin should endeavour to support. See: 
https://tails.boum.org/press/index.en.html

-Kristov

[-- Attachment #2: Type: text/html, Size: 3143 bytes --]

  reply	other threads:[~2014-04-23 20:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 13:30 [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 Warren Togami Jr.
2014-04-22 14:05 ` Wladimir
2014-04-23 20:05 ` Kristov Atlas
2014-04-23 20:28   ` Wladimir
2014-04-23 20:39   ` Warren Togami Jr.
2014-04-23 20:52     ` Kristov Atlas [this message]
2014-04-23 22:28     ` Gregory Maxwell
2014-04-24  1:56       ` Kristov Atlas
2014-04-24  8:02       ` Wladimir
2014-04-24  8:07         ` Wladimir
2014-04-24  8:15         ` Warren Togami Jr.
2014-04-24  8:25           ` Wladimir
2014-04-24 12:18             ` Wladimir
2014-04-25 20:09               ` Kristov Atlas
2014-04-25 20:47                 ` 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=5358280F.2050108@gmail.com \
    --to=kristovatlas@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=wtogami@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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