Re: Error messages and progress report

[Andreas Enge <andreas@enge.fr>]

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

Hello,

I am getting there! Everything compiled, and there is now a hello package.
Or rather, lots of them. /nix/store contains
1 hello-2.8.tar.gz
3 hello-2.8.tar.gz.drv
3 hello-2.8.tar.gz-guile-builder
2 hello-2.8
2 hello-2.8.drv
2 hello-2.8-guile-builder
Altogether 13 files or directories, with different hashes prepended.
Unfortunately, all files have the date "Jan 1 1970". It would be nice to
use the real date of modification instead.


The command
   guix-package -i hello
still produces an error, probably related to making the symlinks
in my own environment:

Backtrace:
In ice-9/boot-9.scm:
 149: 12 [catch #t #<catch-closure 1e035c0> ...]
 157: 11 [#<procedure 1da10f0 ()>]
In unknown file:
   ?: 10 [catch-closure]
In ice-9/boot-9.scm:
  63: 9 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 407: 8 [eval # #]
In unknown file:
   ?: 7 [call-with-input-string "(apply (module-ref (resolve-interface 
'(guix-package)) 'guix-package) (cdr (command-line)))" ...]
In ice-9/command-line.scm:
 174: 6 [#<procedure 1e172c0 at ice-9/command-line.scm:169:3 (port)> 
#<input: string 1bd0340>]
In unknown file:
   ?: 5 [eval (apply (module-ref # #) (cdr #)) #<directory (guile-user) 
1e08d80>]
In ice-9/boot-9.scm:
 149: 4 [catch srfi-34 #<procedure 2365c40 at guix/ui.scm:61:2 ()> ...]
 157: 3 [#<procedure 2364d70 ()>]
In /usr/local/bin/guix-package:
 438: 2 [#<procedure 233d3f0 at /usr/local/bin/guix-package:430:4 ()>]
 379: 1 [process-actions (# #)]
In unknown file:
   ?: 0 [symlink "/nix/store/1n6bpxkjq2w1m8nlyc6c6bpf0y8rspi0-user-
environment" ...]

ERROR: In procedure symlink:
ERROR: In procedure symlink: No such file or directory


The directory
"/nix/store/1n6bpxkjq2w1m8nlyc6c6bpf0y8rspi0-user-environment"
exists, and its subdirectory "bin" contains a link "hello" to
/nix/store/g0izbi5fdmnpgc6mwi45sxks390fkm1v-hello-2.8/bin/hello.

So far, there is no ".guix-profile" in my home directory; but
creating it does not change the error message.

Do I need to do anything special? If yes, it would be good to add a
section "installation" to the manual. I suppose I also need to add a line
to my .bashrc to modify $PATH ?

Andreas

[-- Attachment #2: Type: text/html, Size: 11638 bytes --]