Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1WdEyc-00014f-0X for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 08:25:50 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.179 as permitted sender) client-ip=209.85.223.179; envelope-from=laanwj@gmail.com; helo=mail-ie0-f179.google.com; Received: from mail-ie0-f179.google.com ([209.85.223.179]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WdEyb-00027H-8u for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 08:25:49 +0000 Received: by mail-ie0-f179.google.com with SMTP id lx4so1994822iec.24 for <bitcoin-development@lists.sourceforge.net>; Thu, 24 Apr 2014 01:25:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.85.18 with SMTP id d18mr2090212igz.42.1398327943995; Thu, 24 Apr 2014 01:25:43 -0700 (PDT) Received: by 10.64.22.168 with HTTP; Thu, 24 Apr 2014 01:25:43 -0700 (PDT) In-Reply-To: <CAEz79PqoWOUEwrsaaHjX58QqYbFUdS6k5jg2V9XvOAAUBw00Ug@mail.gmail.com> References: <CAEz79PrAg=yydd3UOk51wGQUWey-KZHUH1Npzwb=qL+6zTj+pQ@mail.gmail.com> <53581D1D.1000709@gmail.com> <CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com> <CAAS2fgSQ6rh1XKao6pv8BmpeRbtqWfUOVF+C1Fi3LEzY1YcPiA@mail.gmail.com> <CA+s+GJDY6c2-fjbL=JcrF3umM4ji8Y5j5ppxX_mAzZdTh1_QRw@mail.gmail.com> <CAEz79PqoWOUEwrsaaHjX58QqYbFUdS6k5jg2V9XvOAAUBw00Ug@mail.gmail.com> Date: Thu, 24 Apr 2014 10:25:43 +0200 Message-ID: <CA+s+GJB6Fucjvcve8QQoWdOz=FG-DMJ7z16PLRS2Q_5ReP4o4A@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: "Warren Togami Jr." <wtogami@gmail.com> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WdEyb-00027H-8u Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 24 Apr 2014 08:25:50 -0000 On Thu, Apr 24, 2014 at 10:15 AM, Warren Togami Jr. <wtogami@gmail.com> wrote: > I now see how it worked with Bitcoin 0.8.6. Lucid has qt-4.6.2. > > It is more than one symbol. It does not seem to be a wise thing to replace > functions beyond the trivial in glibc and libstdc++. Qt is not part of the compiler/build environment. Thus we don't need to resort to those kind of tricks. As I said: we can easily build against Qt 4.6 instead. As said, that wouldn't even need building Qt on linux, just unpacking and exporting the headers. But indeed we need to decide on a cut-off point. I'd have preferred 4.7 or 4.8. Qt 4.6 is *ancient* - it was released in februari 2010. Apart from tails it doesn't seem like anyone is using those old stable distributions on the desktop. Wladimir