From: Carlos O'Donell <carlos@redhat.com>
To: "Andreas K. Hüttel" <dilfridge@gentoo.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches)
Date: Wed, 10 Jan 2024 13:37:18 -0500 [thread overview]
Message-ID: <34c4dc4f-add9-2162-47df-1e995e6c9aae@redhat.com> (raw)
In-Reply-To: <20240102191743.520137-1-dilfridge@gentoo.org>
On 1/2/24 14:17, Andreas K. Hüttel wrote:
> From: "Andreas K. Huettel" <dilfridge@gentoo.org>
I support moving to autoconf 2.72 for glibc 2.40.
I do *not* support moving to autoconf 2.72 for glibc 2.39 (upcoming release).
I think we should not make such changes in the freeze window.
The only impact that I'm aware of is that clang can't build a patched glibc.
Since you're patching glibc to build it with clang you can further patch it
to reconfigure with autoconf 2.72. When we officially support clang for
building glibc then we need to fix this issue.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2024-01-10 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Andreas K. Huettel
2024-01-02 9:14 ` Florian Weimer
2024-01-02 9:21 ` autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release) Andreas K. Huettel
2024-01-02 10:27 ` Florian Weimer
2024-01-02 17:35 ` Paul Eggert
2024-01-02 19:17 ` [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches) Andreas K. Hüttel
2024-01-02 21:30 ` Florian Weimer
2024-01-03 4:13 ` Paul Eggert
2024-01-10 18:37 ` Carlos O'Donell [this message]
2024-01-02 14:39 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Adhemerval Zanella Netto
2024-01-06 12:27 ` Andreas K. Huettel
2024-01-08 12:54 ` Adhemerval Zanella Netto
2024-01-02 15:22 ` H.J. Lu
2024-01-06 22:29 ` Andreas K. Huettel
2024-01-03 21:57 ` enh
2024-01-10 18:38 ` Carlos O'Donell
2024-01-10 20:33 ` Jeff Law
2024-01-11 1:10 ` Palmer Dabbelt
2024-01-12 6:13 ` Palmer Dabbelt
2024-01-11 22:24 ` Freeze for the upcoming glibc 2.39 release - status Andreas K. Huettel
2024-01-12 10:56 ` Adhemerval Zanella Netto
2024-01-12 13:14 ` Xi Ruoyao
2024-01-12 13:25 ` Andreas K. Huettel
2024-01-12 14:23 ` Andreas K. Huettel
2024-01-12 17:19 ` Carlos O'Donell
2024-01-12 17:34 ` Palmer Dabbelt
2024-01-12 18:10 ` Adhemerval Zanella Netto
2024-01-12 22:10 ` Palmer Dabbelt
2024-01-12 22:21 ` Freeze for the upcoming glibc 2.39 release - status (2) Andreas K. Huettel
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=34c4dc4f-add9-2162-47df-1e995e6c9aae@redhat.com \
--to=carlos@redhat.com \
--cc=dilfridge@gentoo.org \
--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).