unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: zamfofex <zamfofex@twdb.moe>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxime Devos" <maximedevos@telenet.be>,
	54832@debbugs.gnu.org
Subject: [bug#54832] [patch] update glibc to 2.35
Date: Tue, 19 Jul 2022 15:16:12 -0400	[thread overview]
Message-ID: <CA+3U0ZnVfd16RArnSVzHUeEf2Zku-sOGeZ6YA+2DpbS-_F106w@mail.gmail.com> (raw)
In-Reply-To: <1143838129.1375777.1658239971665@privateemail.com>

On Tue, Jul 19, 2022 at 12:14 PM zamfofex <zamfofex@twdb.moe> wrote:
>
> > There’s a comment at the top of ‘glibc-dl-cache.patch’ that explains
> > what it does, but see
> > <https://guix.gnu.org/en/blog/2021/taming-the-stat-storm-with-a-loader-cache/>
> > for details.  I can take a look and update it.
>
> It seems we both misinterpreted the diff I had sent originally, as that patch has not actually been removed, but rather its line was changed (it was moved upwards). So good news, no need for changes or further investigation!

I have used your patch to bootstrap with GCC 12 (in order to use both
gcc-12 and llvm-14 in the same profile) and I have found that without
"glibc-ldd-x86_64.patch", sometimes ldd will throw a "not a dynamic
executable" error. I assume the powerpc patch is likewise still
required.

> Thanks for the encouragement! However, since glibc 2.36 releases a few weeks from now, do you feel like it would make sense to wait until then to update it? I suppose it could always be updated again later, but I don’t know if that’s ideal.

I would like to see the 2.35 upgrade since others may benefit before
the 2.36 release and in case of a core-updates merge to master.

Greg




  reply	other threads:[~2022-07-19 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  1:16 [bug#54832] [patch] update glibc to 2.35 zamfofex
2022-04-10 10:16 ` Maxime Devos
     [not found]   ` <1497835452.18920.1649591936889@privateemail.com>
2022-04-24 14:19     ` [bug#54832] Fwd: " zamfofex
2022-04-10 10:17 ` Maxime Devos
2022-04-10 10:18 ` Maxime Devos
2022-05-15 21:31 ` Ludovic Courtès
2022-06-06 12:06   ` zamfofex
2022-07-17 10:06     ` Ludovic Courtès
2022-07-19 14:12       ` zamfofex
2022-07-19 19:16         ` Greg Hogan [this message]
2022-09-01 22:32           ` bug#54832: " Marius Bakke

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+3U0ZnVfd16RArnSVzHUeEf2Zku-sOGeZ6YA+2DpbS-_F106w@mail.gmail.com \
    --to=code@greghogan.com \
    --cc=54832@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=zamfofex@twdb.moe \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).