From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: help-guix@gnu.org
Subject: Re: GUIX_LOCPATH problems with guix on gentoo
Date: Sat, 18 Jun 2016 11:17:49 +0200 [thread overview]
Message-ID: <87r3buonya.fsf@elephly.net> (raw)
In-Reply-To: <20160618083212.GA24472@khazad-dum>
ng0 <ng0@we.make.ritual.n0.is> writes:
> On 2016-06-18(09:45:12+0200), Ricardo Wurmus wrote:
>>
>> Hi,
>>
>> I found it very hard to read this email, because there are so many
>> non-essential things pasted in the body :-/
>
> I wasn't sure what's useful information and what's not.
>
>> I hope I didn't miss anything important while I paged through your
>> email, but one thing stood out to:
>>
>> ng0 <ng0@we.make.ritual.n0.is> writes:
>>
>> > python: stdout/stderr: import json perl: warning: Falling back to the standard locale ("Cpython: stdout/stderr: File "/usr/lib/python2.7/json/__init__.py", line 108, in <module>
>> > python: stdout/stderr: from .decoder import JSONDecoder
>> > python: stdout/stderr: File "/usr/lib/python2.7/json/decoder.py", line 5, in <module>
>> > python: stdout/stderr: import struct
>> > python: stdout/stderr: File "/usr/lib/python2.7/struct.py", line 1, in <module>
>> > python: stdout/stderr: from _struct import *
>> > python: stdout/stderr: ImportError: /usr/lib/python2.7/lib-dynload/_struct.so: undefined symbol: PyUnicode
>>
>> That's not okay. You cannot mix Python from your system with Python
>> from Guix. Do you have system stuff on your PYTHONPATH? Do you have
>> LD_LIBRARY_PATH set? Guix packages should never use system libraries.
>>
>> ~~ Ricardo
>
> In the beginning this was an experiment, to see if Guix
> would run unaffected on a gentoo-hardened kernel.
> I am switching back to a desktop/amd64 profile, will check if
> things changed.
The problem above is unrelated to the kernel. For some reason libraries
from /usr/lib are used. If this really is a Guix package then that’s
wrong.
> Checking right now, LD_LIBRARY_PATH and PYTHONPATH are not set,
> but LIBRARY_PATH is.
LIBRARY_PATH is harmless and only used at compile time.
~~ Ricardo
next prev parent reply other threads:[~2016-06-18 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 10:39 GUIX_LOCPATH problems with guix on gentoo ng0
2016-06-17 18:40 ` ng0
2016-06-18 7:45 ` Ricardo Wurmus
2016-06-18 8:32 ` ng0
2016-06-18 9:17 ` Ricardo Wurmus [this message]
2016-06-18 18:30 ` ng0
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=87r3buonya.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).