📅 Original date posted:2014-04-24
📝 Original message:On Wed, Apr 23, 2014 at 10:02 PM, Wladimir <laanwj at gmail.com> wrote:
> On Thu, Apr 24, 2014 at 12:28 AM, Gregory Maxwell <gmaxwell at gmail.com>
> wrote:
> > On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. <wtogami at gmail.com>
> wrote:
> >> If you are
> >> a rare user who needs Bitcoin-Qt on an incompatible system you can at
> least
> >> build it from source.
> >
> > Tails users usually can't really build it from source— talks is a live
> > boot mostly stateless linux distribution for privacy applications.
> > It's really good in general.
>
> Aside: But is Bitcoin Core a well-suited application for those uses? I
> cannot imagine someone running a full node on a stateless system.
>
> Anyhow: As this is only one symbol, we can probably get rid of it (as
> we didn't use it in 0.8.6?), or put it behind some #ifdef
> COMPATIBILITY_BUILD...
>
> Another option: Instead of statically building it'd be easy enough to
> build against the 4.6 Qt headers instead without even swapping the
> library. Qt is, after all, forward-compatible - between the 4.x
> versions. This will lose some GUI features but if compatibility is
> more important here that's a choice that can be made.
>
> Wladimir
>
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++.
I personally think we need to decide upon a cut-off point beyond which it
makes no sense to add the risk of increased complexity. RHEL6 had qt-4.6.2
as well and I don't think I've heard a single complaint about bitcoin-qt
being broken there given almost nobody uses it as a desktop.
Warren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/feeeee08/attachment.html>;
Warren Togami Jr. [ARCHIVE] /
npub1s5…zxem8
2023-06-07 15:19:20
in reply to nevent1q…jx39
Author Public Key
npub1s5p2xnl52ksr3a4qfa8re5znmja46ugm3x3ayy0x2c2mqrsw6ewsmzxem8Published at
2023-06-07 15:19:20Event JSON
{
"id": "6aa3c3db9b747e67e3d9e60223ba6cf40c83e717c89c13d4da60ffc5abe1f045",
"pubkey": "8502a34ff455a038f6a04f4e3cd053dcbb5d711b89a3d211e65615b00e0ed65d",
"created_at": 1686151160,
"kind": 1,
"tags": [
[
"e",
"32a9c22b7e6c52f4ef70051f92bdc18644b13f1c93ed2a5c2cefd9e927d70b7e",
"",
"root"
],
[
"e",
"852a1188242daf9db6a2893e2a04727e56a7dc6f4638407f91be31f739527426",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2014-04-24\n📝 Original message:On Wed, Apr 23, 2014 at 10:02 PM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\n\u003e On Thu, Apr 24, 2014 at 12:28 AM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e\n\u003e wrote:\n\u003e \u003e On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. \u003cwtogami at gmail.com\u003e\n\u003e wrote:\n\u003e \u003e\u003e If you are\n\u003e \u003e\u003e a rare user who needs Bitcoin-Qt on an incompatible system you can at\n\u003e least\n\u003e \u003e\u003e build it from source.\n\u003e \u003e\n\u003e \u003e Tails users usually can't really build it from source— talks is a live\n\u003e \u003e boot mostly stateless linux distribution for privacy applications.\n\u003e \u003e It's really good in general.\n\u003e\n\u003e Aside: But is Bitcoin Core a well-suited application for those uses? I\n\u003e cannot imagine someone running a full node on a stateless system.\n\u003e\n\u003e Anyhow: As this is only one symbol, we can probably get rid of it (as\n\u003e we didn't use it in 0.8.6?), or put it behind some #ifdef\n\u003e COMPATIBILITY_BUILD...\n\u003e\n\u003e Another option: Instead of statically building it'd be easy enough to\n\u003e build against the 4.6 Qt headers instead without even swapping the\n\u003e library. Qt is, after all, forward-compatible - between the 4.x\n\u003e versions. This will lose some GUI features but if compatibility is\n\u003e more important here that's a choice that can be made.\n\u003e\n\u003e Wladimir\n\u003e\n\nI now see how it worked with Bitcoin 0.8.6. Lucid has qt-4.6.2.\n\nIt is more than one symbol. It does not seem to be a wise thing to replace\nfunctions beyond the trivial in glibc and libstdc++.\n\nI personally think we need to decide upon a cut-off point beyond which it\nmakes no sense to add the risk of increased complexity. RHEL6 had qt-4.6.2\nas well and I don't think I've heard a single complaint about bitcoin-qt\nbeing broken there given almost nobody uses it as a desktop.\n\nWarren\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/feeeee08/attachment.html\u003e",
"sig": "72f5d797c310ee8e3c0994218a8c8c83175086fdaaf99b7dbae99cfec682e47baff764e25888d90443ee5eb2a88770d7b6558c81b607bf0b0db49689f34b3226"
}