[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?
From: |
Thompson, David |
Subject: |
Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt? |
Date: |
Wed, 10 Feb 2016 09:25:06 -0500 |
On Wed, Feb 10, 2016 at 9:17 AM, Ludovic Courtès <address@hidden> wrote:
> Christopher Allan Webber <address@hidden> skribis:
>
>> Just for posterity, Dave helped me figure out what was wrong. I missed
>> putting guile-2.0 in my inputs. Critical! Well, once I did that,
>> things were fine!
>
> Indeed. However, since Haunt ships a command-line tool, we should fix
> the Haunt package in Guix to wrap ‘bin/haunt’ such that the tool has
> GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH properly set.
>
> Done in 4ecbf6d. I think it should be fixed upstream though. :-)
I don't understand why this would require an upstream fix for what
seems to be a Guix-specific quirk. Could you elaborate?
> BTW, ‘guix build haunt --with-input=guile=guile-next’ fails at configure
> time (it insists on 2.0.)
Thanks, Ludo. I noticed that in another project of mine. I guess I'm
using the wrong autoconf macro to check for the version being greater
than 2.0.x. I'll have to figure out what the correct thing is.
- Dave
- Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Christopher Allan Webber, 2016/02/09
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Christopher Allan Webber, 2016/02/09
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Ludovic Courtès, 2016/02/10
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?,
Thompson, David <=
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Ludovic Courtès, 2016/02/11
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Thompson, David, 2016/02/12
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Christopher Allan Webber, 2016/02/14
- Re: Any clue why $GUILE_LOAD_PATH not propagated with Haunt?, Ludovic Courtès, 2016/02/23