unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "André A. Gomes" <andremegafone@gmail.com>
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, 09 Jan 2022 22:37:06 +0300	[thread overview]
Message-ID: <878rvovgyl.fsf@gmail.com> (raw)
In-Reply-To: <87v8ys945o.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 09 Jan 2022 19:03:33 +0100")

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?  I installed it so that I could read the docs from the comfort
of the info program.

My question follows from the fact that I observe the following message
lately.  It also reminds me that I should pack QMK for guix.

--8<---------------cut here---------------start------------->8---
Warning: Could not import qmk.cli.console: ImportError, Unable to load
any of the following libraries:libhidapi-hidraw.so libhidapi-hidraw.so.0
libhidapi-libusb.so libhidapi-libusb.so.0 libhidapi-iohidmanager.so
libhidapi-iohidmanager.so.0 libhidapi.dylib hidapi.dll libhidapi-0.dll
--8<---------------cut here---------------end--------------->8---

Thanks.


--
André A. Gomes
"Free Thought, Free World"


  parent reply	other threads:[~2022-01-09 19:37 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 [this message]
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=878rvovgyl.fsf@gmail.com \
    --to=andremegafone@gmail.com \
    --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).