Transaction

bea7a6aec558fbf43f748ecd2b3f1573f47ff2feb413aa2a683d6a5f385c9a6c
Timestamp (utc)
2024-03-26 23:46:21
Fee Paid
0.00000026 BSV
(
0.00881717 BSV
-
0.00881691 BSV
)
Fee Rate
10.19 sat/KB
Version
1
Confirmations
93,825
Size Stats
2,550 B

2 Outputs

Total Output:
0.00881691 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMú<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=612.msg6545#msg6545">Quote from: jgarzik on July 29, 2010, 11:22:54 PM</a></div><div class="quote">Yeah, some sort of virtual machine like qemu/KVM is really the best way to go, for older distro support.</div><br/>Just to clear up any (potential) misconception, from the use of the phrase "for older distro support". &nbsp;Just because you compiled your application with an older distro doesn't mean it doesn't work on a newer distro many libraries are backwardly compatible in that way.<br/><br/>When they do change major DSO version (incompatible or breaking changes) some distributions still provide the ability to install the older compat libraries. &nbsp;Its easier for a new distro to find older compat libraries than it is for an older distro to use a newer GLIBC.<br/><br/><br/>I am somewhat asserting that, if it is indeed possible to compile with older versions (because the features the newer versions add are not actually required by the application) then this version that should be made available via a single binary download (since it will work with the widest audience).<br/><br/><br/>Also to repeat, that the OpenSUSE Build Service is like a remote virtualized service which you can use compile your application on multiple major distributions and the output is a bunch of packages tailored to suit each distro.<br/><br/><br/>The clear problem I see is not with the support for aux lbiraries (Xlib,GTK+,OpenSSL,freetype) but with basic GLIBC and GCC libstdc++. &nbsp;The problem with this is that you can't expect to simply place the DLLs you need in the same directory as the bitcoin executable and fix up LD_LIBRARY_PATH (man ld.so) so it can see them.<br/><br/>For example lets say that it was compiled with an older GTK+ than is available for your distribution of choice (a DSO major release change, this is indicated in the 2nd "0" in the /usr/lib{,64}/libgtk+-x11-2.0.so.0.1800.9) - note it is still zero, this indicates long term stability re-backward compatibility. &nbsp;Well it is possible to easily fix this problem without installing the libraries by fixing them up with LD_LIBRARY_PATH. &nbsp;But for glibc solving the problem in this way is not so straightforward.<br/></div> text/html
    https://whatsonchain.com/tx/bea7a6aec558fbf43f748ecd2b3f1573f47ff2feb413aa2a683d6a5f385c9a6c