all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: guix-devel@gnu.org, 48941@debbugs.gnu.org
Subject: Re: bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs
Date: Thu, 22 Jul 2021 22:34:41 -0700	[thread overview]
Message-ID: <87v9511tla.fsf@gmail.com> (raw)
In-Reply-To: <GijrfHfxGeVNJVWlkkOpscqh2dekCZhqP6OG4ihBNoSCZlxk0evgqhgCT4WEpHdpRsEk_tBHC0rsTHHgl20vhEBt8UJHnsNNglj5-SF4JrI=@protonmail.com> (Kaelyn's message of "Wed, 21 Jul 2021 14:31:25 +0000")

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

Hi Kaelyn,

Thank you for the reply.

Kaelyn <kaelyn.alexi@protonmail.com> writes:

> Are you using Guix on a foreign distro? This line looks like your
> distro's normal libc.so was being used and it was from glibc-2.31 or
> older. The x86-64 systems I have that run pure Guix don't have any
> /lib*/ directories. You might try running gdb with
> LD_LIBRARY_PATH=/gnu/store/kmblbljiygayhlc5gb02an9imhy90ws9-glibc-2.33/lib
> to have the Guix libc.so picked up before the other one. HTH

Yes, I'm using Guix on a foreign distro.  It isn't clear to me what is
trying to access the /lib directories.  That's what I'm trying to figure
out.  In a --pure environment using only Guix-built tools, one would
expect that I would not have to set LD_LIBRARY_PATH.  However, if I
can't figure it out, that's another trick I can try.

-- 
Chris

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

  parent reply	other threads:[~2021-07-23  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  5:08 bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs Chris Marusich
2021-07-21 14:31 ` Kaelyn
2021-07-22 18:35   ` Thiago Jung Bauermann
2021-07-23  6:01     ` Chris Marusich
2021-07-23  5:34   ` Chris Marusich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-10  4:21 Chris Marusich
2021-06-12  2:56 ` Chris Marusich

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=87v9511tla.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=48941@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /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.