all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: "libc.so.6: version `GLIBC_2.33' not found" with guix time-machine --channels
Date: Sun, 09 Jan 2022 21:51:55 +0100	[thread overview]
Message-ID: <87r19g8wdo.fsf@elephly.net> (raw)
In-Reply-To: <878rvovgyl.fsf@gmail.com>


André A. Gomes <andremegafone@gmail.com> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Wiktor Żelazny <wz@freeshell.de> writes:
>>
>>> One more thing: the problem started after I had had to roll-back a
>>> segfaulting guix build.
>>
>> Guix should not segfault.  A segfault is always a severe bug.  Or it’s
>> an indication that LD_LIBRARY_PATH is set, forcing incompatible
>> libraries to be used.
>>
>> Is LD_LIBRARY_PATH set?  Do you have glibc installed in your default
>> profile?
>
> Could you please explain me why having glicb in the default profile is a
> bad idea?

It’s not a bad idea in general, but in combination with other
environment variables it might be.  I’m just trying to get a little more
information on what the problem might be.

-- 
Ricardo


  reply	other threads:[~2022-01-09 20:52 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
2022-02-03 14:18         ` Wiktor Żelazny
2022-01-09 19:37       ` André A. Gomes
2022-01-09 20:51         ` Ricardo Wurmus [this message]
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

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

  git send-email \
    --in-reply-to=87r19g8wdo.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=andremegafone@gmail.com \
    --cc=help-guix@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.