Avoid specifying old symbol versions for compatibility, by just not specifying a version at all #14044

issue luke-jr opened this issue on August 24, 2018
  1. luke-jr commented at 8:07 AM on August 24, 2018: member

    Apparently unversioned symbol references just bind to any random version found: https://stackoverflow.com/a/19364771

    In theory, this can be used to avoid specifying (and using!) the oldest glibc symbols. (Possibly it might even enable using our binaries on non-glibc systems as well?)

    Only problem is, I can't see a way to instruct ld to do this. The StackOverflow answer above solves it by building the target library without symbols, but so long as we're using Ubuntu-packaged libraries, we can't really do that for glibc.

    At the very least, I guess this can be solved when we finally build our own libc from scratch, but it'd be nice to find a proper solution.

  2. MarcoFalke added the label Build system on Aug 24, 2018
  3. ryanofsky commented at 5:53 PM on August 24, 2018: member

    This is probably a dumb question, but just for clarity, what's a symptom (or possible symptom) of this problem?

  4. MarcoFalke commented at 10:30 PM on April 26, 2020: member

    The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

    Closing due to lack of interest. Pull requests with improvements are always welcome.

  5. MarcoFalke closed this on Apr 26, 2020

  6. DrahtBot locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-14 15:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me