Efraim Flashner <efr...@flashner.co.il> writes:
> On Tue, 09 Feb 2016 02:31:51 +0100
> Nils Gillmann <niaster...@grrlz.net> wrote:
>
>> Leo Famulari <l...@famulari.name> 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.
>>
>>
>> niasterisk@khazad-dum ~$ 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
>> niasterisk@khazad-dum ~$ lispf4
>> Can't open 'SYSATOMS'
>> niasterisk@khazad-dum ~$ 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'").
Should I try other permission levels like 755 now until I find
one which works for guix? 644 was the one which worked in $HOME
in debian, that's my only build and succesful run experience with
lispf4.
what do you think?
--
ng
