[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Everything segfaults

From: Paul van der Walt
Subject: Re: Everything segfaults
Date: Tue, 14 Jun 2016 20:30:51 +0200
User-agent: mu4e 0.9.17; emacs 24.5.1

Hey Andreas!

Sorry for the delay!  Busy busy.

On 2016-06-09 at 19:28, quoth Andreas Enge:
> the following looks very strange:
>> [very strange output]
> Your Guix less seems to open libraries from your Arch system, which are
> incompatible. Did you set LD_LIBRARY_PATH?
> Maybe you could try "ldd /home/paul/.guix-profile/bin/less".

If i open a terminal, then


Here's some output:

Case A:
$ ldd .guix-profile/bin/less                                                    
             (0x00007ffe775d7000) => /usr/lib/ (0x00007f8401bc3000) => /usr/lib/ (0x00007f84019ad000) => /usr/lib/ (0x00007f840160c000)

Case B:
$ LD_LIBRARY_PATH="~/.guix-profile/lib" ldd .guix-profile/bin/less (0x00007ffe7cedb000) => 
(0x00007fbc6dbdb000) => 
(0x00007fbc6d9c5000) => 

(when i try setting LD_..="~/.guix-profile/lib:$LD_..", that is, i only
prepend the Guix lib path, then i get the same output from ldd as in
case A -- is that what i expect?)

So there's definitely something funny going on with LD_LIBRARY_PATH
indeed.  But here's another stupid question: surely if i want arbitrary
Guix binaries to work on my system i'd apparently (?) have to put
something like

    export LD_LIBRARY_PATH="$HOME/.guix-profile/lib"

in my .xinitrc, but that would surely break other binaries (those
installed by my usual package manager)?  And if i put

    export LD_LIBRARY_PATH="$HOME/.guix-profile/lib:$LD_LIBRARY_PATH"

in my .xinitrc, then as in case A, surely i won't have fixed my issue?

Sorry to be so thick about this!

Kind regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]