[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: add lispf4
From: |
Ricardo Wurmus |
Subject: |
Re: [PATCH] gnu: add lispf4 |
Date: |
Sun, 14 Feb 2016 09:10:30 +0100 |
User-agent: |
mu4e 0.9.13; emacs 24.5.1 |
Nils Gillmann <address@hidden> writes:
> Efraim Flashner <address@hidden> writes:
>
>> On Tue, 09 Feb 2016 02:31:51 +0100
>> Nils Gillmann <address@hidden> wrote:
>>
>>> Leo Famulari <address@hidden> writes:
>>>
>>> [...]
>>> [...]
>>> [...]
>>> [...]
>>> [...]
>>> [...]
>>> [...]
>>> [...]
>>>
>>> Thanks!
>>>
>>> But now as I did guix pull and installed it from there, and do
>>> not run it inside guix environment, I encounter an error I did
>>> not see coming as it worked in the environment.
>>>
>>>
>>> address@hidden ~$ guix package -i lispf4
>>> The following package will be installed:
>>> lispf4 0.0.0-1-174d876
>>> /gnu/store/7rkw1rhn4ijap9b936waspki03260lpb-lispf4-0.0.0-1-174d876
>>>
>>> 56 packages in profile
>>> address@hidden ~$ lispf4
>>> Can't open 'SYSATOMS'
>>> address@hidden ~$ ls -al
>>> /gnu/store/7rkw1rhn4ijap9b936waspki03260lpb-lispf4-0.0.0-1-174d876/bin/
>>> total 200
>>> dr-xr-xr-x 2 root guixbuild 4096 Jan 1 1970 ./
>>> dr-xr-xr-x 3 root guixbuild 4096 Jan 1 1970 ../
>>> -r--r--r-- 3 root guixbuild 94972 Jan 1 1970 BASIC.IMG
>>> -r-xr-xr-x 7 root guixbuild 92088 Jan 1 1970 lispf4
>>> -r--r--r-- 7 root guixbuild 2105 Jan 1 1970 SYSATOMS
>>>
>>> I checked ~/.guix-profile/bin/ and it's there, all three files.
>>> For what I know, SYSATOMS includes allowed commands, that's it.
>>> My guix checkout I develop with is in my home folder, permissions
>>> for my daily user and all checked in guix environment.
>>>
>>> Any Ideas?
>>
>> If you replace the install phase sometimes you have to change the permissions
>> yourself. Try searching for #o555.
>
> Okay, I just tried #o555 and #o644 in individual builds for both
> files. Both builds produced the same mistake which currently
> keeps lispf4 from running ("can't open 'SYSATOMS'").
Could it be a search-path problem? Try running
strace -f lispf4
to see where lispf4 looks for SYSATOMS and what the exact error is as it
tries to open the file. Does it find it at all?
~~ Ricardo
- Re: [PATCH] gnu: add lispf4, (continued)
- Re: [PATCH] gnu: add lispf4, Leo Famulari, 2016/02/07
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/08
- Re: [PATCH] gnu: add lispf4, Leo Famulari, 2016/02/08
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/08
- Re: [PATCH] gnu: add lispf4, Efraim Flashner, 2016/02/09
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/09
- Re: [PATCH] gnu: add lispf4, Leo Famulari, 2016/02/10
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/10
- Re: [PATCH] gnu: add lispf4, Leo Famulari, 2016/02/11
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/13
- Re: [PATCH] gnu: add lispf4,
Ricardo Wurmus <=
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/14
- Re: [PATCH] gnu: add lispf4, Ricardo Wurmus, 2016/02/14
- Re: [PATCH] gnu: add lispf4, Nils Gillmann, 2016/02/13