From: Chris Packham <judge.packham@gmail.com>
To: Boran Car <boran.car@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Chris Packham via Libc-help <libc-help@sourceware.org>
Subject: Re: Build hangs on stdio-common for glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427
Date: Wed, 20 Sep 2023 09:08:51 +1200 [thread overview]
Message-ID: <CAFOYHZD_LMTbVWiAAqoLEOcOqL717RwXeVevvRQU2YrZLTuOVg@mail.gmail.com> (raw)
In-Reply-To: <CAPa+MXkb4LEWBZWzn9Bhs=TZeo8xqYkrTdMiN5ToaJmkFLOqjA@mail.gmail.com>
On Tue, Sep 19, 2023 at 4:06 AM Boran Car <boran.car@gmail.com> wrote:
>
> There's definitely interest in fixing this, at least from my side, but
> I do need handholding through the build-system. If a Makefile can be
> back-ported, even better. There's still interest in pre 2.31 glibcs
> out there, and Buildroot and crosstools-NG were definitely not made to
> build their own Make as part of the process.
Heh. That's exactly the workaround we put in for crosstool-ng
https://github.com/crosstool-ng/crosstool-ng/commit/e63c40854
I didn't stare too long at
https://sourceware.org/git/?p=glibc.git;a=commit;h=37f802f864006 which
is the change that "fixes" the issue. Fixing the make issue appears to
be more of a side effect than the actual intent of the change. Might
be work seeing how cleanly that commit cherry-picks onto older
releases.
next prev parent reply other threads:[~2023-09-19 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 18:53 Boran Car
2023-09-17 19:21 ` Boran Car
2023-09-18 8:16 ` Chris Packham
2023-09-18 11:43 ` Florian Weimer
2023-09-18 16:06 ` Boran Car
2023-09-19 21:08 ` Chris Packham [this message]
2023-10-01 11:48 ` Boran Car
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=CAFOYHZD_LMTbVWiAAqoLEOcOqL717RwXeVevvRQU2YrZLTuOVg@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=boran.car@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-help@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).