From: Szabolcs Nagy <nsz@port70.net>
To: Andrew Kelley <andrew@ziglang.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] features: version-gate _DYNAMIC_STACK_SIZE_SOURCE
Date: Sat, 29 Jan 2022 11:41:51 +0100 [thread overview]
Message-ID: <20220129104151.GE1320090@port70.net> (raw)
In-Reply-To: <a994e1fe-fede-00d5-da86-4f1c6a81edcb@ziglang.org>
* Andrew Kelley <andrew@ziglang.org> [2022-01-28 21:15:36 -0700]:
> On 1/28/22 21:04, Andrew Kelley wrote:
> > Downstream we also have a patch that removes the __GLIBC_MINOR__
> > preprocessor definition. Instead, we pass it on the command line.
> >
> > https://github.com/ziglang/zig/commit/4d48948b526337947ef59a83f7dbc81b70aa5723
> >
> >
> > The Zig project aims to support targeting many versions of glibc; not
> > only the latest one. Our strategy is multi-faceted. For the shared
> > objects, there is this project:
> > https://github.com/ziglang/glibc-abi-tool/
> >
> > And then we have the headers. For the most part, the latest glibc
> > headers are still correct for targeting systems with older glibc
new headers may rely on new symbols, behaviours and abi that
did not exist in an old glibc.
the only way multiple glibc versions are supported at runtime
is to compile against old glibc and run the binary against a
newer one. not the other way around.
and you cannot detect at compile time what will be the glibc
version at runtime, so version checking does not help.
what problem are you solving by passing __GLIBC_MINOR__ at
compile time?
next prev parent reply other threads:[~2022-01-29 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 2:37 Andrew Kelley
2022-01-29 3:00 ` H.J. Lu
2022-01-29 4:04 ` Andrew Kelley
2022-01-29 4:15 ` Andrew Kelley
2022-01-29 10:41 ` Szabolcs Nagy [this message]
2022-02-01 16:37 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220129104151.GE1320090@port70.net \
--to=nsz@port70.net \
--cc=andrew@ziglang.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).