all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: guix-devel@gnu.org
Subject: Re: Support for glibc 2.35
Date: Wed, 06 Apr 2022 10:26:44 +0200	[thread overview]
Message-ID: <87tub6hb23.fsf@gnu.org> (raw)
In-Reply-To: <86a6czq8n8.fsf@163.com> (Zhu Zihao's message of "Wed, 06 Apr 2022 09:46:55 +0800")

Hi,

Zhu Zihao <all_but_last@163.com> skribis:

> Olivier Dion via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes:
>
>> Hello,
>>
>> I would like to know if there's plan to add glibc@2.35 soon to the guix
>> channel?
>
> I'm afraid not. Bumping the version of glibc is not a trivial package
> update in Guix, it means almost all packages need to rebuild (rebuild
> the world).

Right, so we update it in a separate branch, ‘core-updates’, together
with other “core” packages.  The branch gets merged roughly once every 6
months, so one needs to be patient (such updates take a non-negligible
amount of QA work!).

> If you really need it, you may inherit from a existing glibc package,
> update to 2.35 and use it. But you may need extra patches to make it
> work well.

Yes, you can do that, use ‘make-gcc-toolchain’ (say) to build a custom
toolchain, and use ‘--with-c-toolchain’ to use that.

HTH!

Ludo’.


      parent reply	other threads:[~2022-04-06  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  1:23 Support for glibc 2.35 Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-04-06  1:46 ` Zhu Zihao
2022-04-06  2:03   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-04-06  8:26   ` Ludovic Courtès [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=87tub6hb23.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=all_but_last@163.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.