Re: [PATCH] website: Add support for Haunt.

[Mathieu Lirzin]

Hi,

Sorry for my late answer.

Alex Vong <address@hidden> writes:

> I have followed your instruction but there is still a problem. After I
> run `guix build -f guix.scm`, I try to run:
>
> address@hidden:~$
> /gnu/store/n8r3jj2jhs5xvpcf2d4crqk706089sxa-haunt-0.1/bin/haunt --help
> Backtrace:
> In ice-9/boot-9.scm:
>  157: 17 [catch #t #<catch-closure 2147840> ...]
> In unknown file:
>    ?: 16 [apply-smob/1 #<catch-closure 2147840>]
> In ice-9/boot-9.scm:
>   63: 15 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
>  432: 14 [eval # #]
> In ice-9/boot-9.scm:
> 2401: 13 [save-module-excursion #<procedure 2164940 at
> ice-9/boot-9.scm:4045:3 ()>]
> 4050: 12 [#<procedure 2164940 at ice-9/boot-9.scm:4045:3 ()>]
> 1724: 11 [%start-stack load-stack ...]
> 1729: 10 [#<procedure 217aea0 ()>]
> In unknown file:
>    ?: 9 [primitive-load
> "/gnu/store/n8r3jj2jhs5xvpcf2d4crqk706089sxa-haunt-0.1/bin/haunt"]
> In ice-9/eval.scm:
>  505: 8 [#<procedure 20186a0 at ice-9/eval.scm:499:4 (exp)> (use-modules #)]
> In ice-9/psyntax.scm:
> 1106: 7 [expand-top-sequence ((use-modules (haunt ui))) () ...]
>  989: 6 [scan ((use-modules (haunt ui))) () ...]
>  279: 5 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
> In ice-9/boot-9.scm:
> 3597: 4 [process-use-modules (((haunt ui)))]
>  702: 3 [map #<procedure 20d9d00 at ice-9/boot-9.scm:3597:25 (mif-args)> 
> ((#))]
> 3598: 2 [#<procedure 20d9d00 at ice-9/boot-9.scm:3597:25 (mif-args)>
> ((haunt ui))]
> 2867: 1 [resolve-interface (haunt ui) #:select ...]
> In unknown file:
>    ?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (haunt ui)) #f]
>
> ERROR: In procedure scm-error:
> ERROR: no code for module (haunt ui)
>
> Thanks for your help!
>
> Cheers,
> Alex

The problem is that your guile related environment variables are not
correctly set to find random guile modules in /gnu/store.  Since you
have (correctly) defined:

  GUIX_PROFILE="$HOME/.guix-profile" \
    source "$HOME/.guix-profile/etc/profile"

It is required to install the package in your profile with:

  guix package -i $(guix build -f guix.scm)

As a result ~/.guix-profile/share/guile/site/2.0/haunt will be created
and GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH will be able to find
the (haunt ...) modules when XXX/bin/haunt is executed.

Does it makes sense?

--
Mathieu Lirzin