From: Sam James <sam@gentoo.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "Florian Weimer" <fw@deneb.enyo.de>, "Sam James" <sam@gentoo.org>,
"Frank Scheiner" <frank.scheiner@web.de>,
"Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
"Tomáš Glozar" <tglozar@gmail.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] Remove ia64-linux-gnu
Date: Mon, 06 Nov 2023 16:33:08 +0000 [thread overview]
Message-ID: <875y2eon88.fsf@gentoo.org> (raw)
In-Reply-To: <fca3dd5b-58b1-ab6f-bb7e-0ef17a872d11@redhat.com>
Carlos O'Donell <carlos@redhat.com> writes:
> On 11/4/23 17:44, Florian Weimer wrote:
>> * Sam James:
>>
>>> Also, I worry that this might make things tricky to backport later for
>>> older glibc branches. Regardless of what happens with ia64 being
>>> maintained out of tree or not, we don't intend on removing it from Gentoo
>>> immediately - possibly (although I don't make a promise here) as late as
>>> when the last LTS kernel supporting it ages out. I'd prefer to not have
>>> to pin ia64 to an older glibc and keep testing that branch just for one
>>> arch.
>>
>> Could those who want to keep ia64 support at least set up a
>> cross-builder (preferably both post-commit and pre-commit)? Once
>> kernel support is gone from mainline, we'll have to remove it from the
>> default build-many-glibcs.py configuration, so we'll lose build
>> coverage.
>>
>
> The follow-on problem is that there is no upstream ABI, and so downstream has to make
> those ABI decisions? I would rather we *not* make those ABI decisions, and if ia64
> is ever put back into upstream we can just "catch up" and adopt the ABI pieces as they
> are defined by the official upstream kernel.
>
> I think the best option here is for downstreams to pin glibc at 2.38 and use that for
> the lifetime of the Linux 6.6 LTS, which is likely all the way to 2028.
I wanted to raise the point but I don't really have an objection as long
as we've considered the bits I raised (and we have). Thanks.
next prev parent reply other threads:[~2023-11-06 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 19:02 Adhemerval Zanella
2023-11-04 19:59 ` Frank Scheiner
2023-11-04 20:14 ` Sam James
2023-11-04 21:44 ` Florian Weimer
2023-11-06 12:29 ` Adhemerval Zanella Netto
2023-11-06 15:04 ` Carlos O'Donell
2023-11-06 16:28 ` Florian Weimer
2023-11-06 16:54 ` Adhemerval Zanella Netto
2023-11-06 16:33 ` Sam James [this message]
2023-11-06 11:48 ` Adhemerval Zanella Netto
2023-11-06 15:48 ` Carlos O'Donell
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=875y2eon88.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=frank.scheiner@web.de \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=tglozar@gmail.com \
/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).