unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Wiktor Żelazny" <wz@freeshell.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: "libc.so.6: version `GLIBC_2.33' not found" with guix time-machine --channels
Date: Sun, 9 Jan 2022 19:49:29 +0100	[thread overview]
Message-ID: <20220109184929.grglktw5aubnwxgf@wzguix> (raw)
In-Reply-To: <87v8ys945o.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

On Sun, Jan 09, 2022 at 07:03:33PM +0100, Ricardo Wurmus wrote:
>
> Wiktor Żelazny <wz@freeshell.de> writes:
>
> > One more thing: the problem started after I had had to roll-back a
> > segfaulting guix build.
>
> Is LD_LIBRARY_PATH set

Not anymore.

   $ set | grep LD_LIBRARY_PATH
   [nothing]

> Do you have glibc installed in your default profile?

Nope.

   $ guix package --list-installed | grep glibc
   [nothing]

I’ve got glibc-locales in /etc/config.scm.

WŻ

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2022-01-09 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 15:11 "libc.so.6: version `GLIBC_2.33' not found" with guix time-machine --channels Wiktor Żelazny
2022-01-08 18:50 ` Leo Famulari
2022-01-09 17:57   ` Wiktor Żelazny
2022-01-09 18:03     ` Ricardo Wurmus
2022-01-09 18:49       ` Wiktor Żelazny [this message]
2022-02-03 14:18         ` Wiktor Żelazny
2022-01-09 19:37       ` André A. Gomes
2022-01-09 20:51         ` Ricardo Wurmus
2022-01-09 18:09     ` Tobias Geerinckx-Rice
2022-01-10 19:04       ` Wiktor Żelazny

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=20220109184929.grglktw5aubnwxgf@wzguix \
    --to=wz@freeshell.de \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).