Transaction

b4ecebfdaabc0abfa904f013543ade276d17dae6892f8197cb177b85fd39df24
Timestamp (utc)
2024-03-24 17:00:36
Fee Paid
0.00000029 BSV
(
0.01006859 BSV
-
0.01006830 BSV
)
Fee Rate
10.26 sat/KB
Version
1
Confirmations
98,049
Size Stats
2,824 B

2 Outputs

Total Output:
0.01006830 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM <div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=612.msg6579#msg6579">Quote from: jgarzik on July 30, 2010, 02:05:57 AM</a></div><div class="quote">Most of what you say is true, but, bitcoin tends to be built against very specific versions of its dependent libs.&nbsp; Due to that, one tends to build bitcoin against custom compiled libs, regardless of underlying OS version.&nbsp; That practice makes glibc the primary compatibility worry.</div><br/><br/>Please cite exactly which library is using which feature of very recent glibc version (or any library for that matter) ? &nbsp;(just so we can all understand the problem in the way you state).<br/><br/><br/>From what I can see wxWidgets and boost are linked statically. &nbsp;I guess this is due to the "build against very specific versions of its dependent libs". &nbsp;But from what I can see there is _NO_ need for either of thes libraries to use a recent glibc, wxWidgets for example only has a check for glibc 2.1 or newer (during its ./configure). &nbsp;But it is not clear which features of wxWidgets 2.9.0 and/or boost 1.40.0 require the use of a glibc say above version 2.5 (which is also pretty old, but pretty compatibile). &nbsp;I have sucessfully been able to build these versions (of wxWidgets/boost) against glibc 2.5.<br/><br/>I believe this can be confirmed by the use of -Bstatic in "src/makefile.unix".<br/><br/><br/>The only reason that glibc is a "compatibility worry" (as you put it) is because the project was build on a very new linux system. &nbsp;This forces all the downloaders to have as-new-a linux system as the build system in order to run it. &nbsp;This is not because there is some intrinsic compatibility worry as you describe it.<br/><br/><br/>I think I have created a custom wxWidgets 2.9.x build on OpenSUSE build service (OBS). &nbsp;I shall have a go with "boost" over the new few hours if all goes well. &nbsp;Then I can commit bitcoind package and get openSuSE builds. &nbsp;Then I can enable other distribution repos (CentOS, Ubuntu, SLE, Fedora, etc...).<br/><br/>Can anyone confirm if boost "1.40.0" is needed or just "1.40.0 or newer" ? &nbsp;since 1.42.x is current (and that is already available for a number of platforms as packages). &nbsp;Can anyone explain the story behind this matter.<br/><br/>With wxWidgets 2.9.x is a development series so it is pre-release, so that is clear cut that a custom version needs to be built to get access to pre-release versions. &nbsp;But this problem I have solved in an OBS build.</div> text/html
    https://whatsonchain.com/tx/b4ecebfdaabc0abfa904f013543ade276d17dae6892f8197cb177b85fd39df24