From: Florian Weimer <fweimer@redhat.com>
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: Tue, 01 Feb 2022 17:37:19 +0100 [thread overview]
Message-ID: <87ee4m35mo.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <f9344eeb-4072-8e2d-dd0f-0b8411e0ec8f@ziglang.org> (Andrew Kelley's message of "Fri, 28 Jan 2022 21:04:01 -0700")
* Andrew Kelley:
> 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
> versions. Some of the other usages of __GNUC_PREREQ look to be
> supporting this use case to me. An occasional patch such as this one
> is needed to make it work correctly, however.
__GNUC_PREREQ certainly does not work for this, it's for GCC version
checks.
Why do you need *C* header files?
Thanks,
Florian
prev parent reply other threads:[~2022-02-01 16:37 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
2022-02-01 16:37 ` Florian Weimer [this message]
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=87ee4m35mo.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--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).