Danny Milosavljevic skribis:
> On Wed, 07 Sep 2016 22:49:12 +0200
> l...@gnu.org (Ludovic Courtès) wrote:
>> I don’t know.
>
>>What you describe sounds a lot like a search path issue.
>
> It is a search path issue.
>
> Does package-for-guile-2.2 take it into account?
>
> Your E-mail contains:
>
>
On Wed, 7 Sep 2016 23:15:22 +0200
Danny Milosavljevic wrote:
>export PATH="foo/bin${PATH:+:}$PATH"
>export
> GUILE_LOAD_PATH="foo/share/guile/site/2.0${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
>export
> GUILE_LOAD_COMPILED_PATH="foo/lib/guile/2.0/ccache:foo/share/guile/site/2.0${GUILE_L
Hi,
On Wed, 07 Sep 2016 22:49:12 +0200
l...@gnu.org (Ludovic Courtès) wrote:
> I don’t know.
>What you describe sounds a lot like a search path issue.
It is a search path issue.
Does package-for-guile-2.2 take it into account?
Your E-mail contains:
The following environment variable definitio
Hello,
Danny Milosavljevic skribis:
> does that mean we can fix guile-emacs?
I don’t know. What you describe sounds a lot like a search path issue.
This works well (albeit slowly):
guix environment --ad-hoc --pure guile-emacs -- emacs -q
Ludo’.
Hi Ludo,
does that mean we can fix guile-emacs?
I've just updated to the latest version that is in Guix and I get:
Throw to key system-error with args ("load-thunk-from-memory" "A" ("No such
file or directory") (2))Threads explicit registering is not previously enabled.
The same problem existe
Ludovic Courtès writes:
> Hello!
>
> The Guile 2.2 series is becoming a reality, so time has come to provide
> packages built with/for Guile 2.2 (aka. 2.1, aka. ‘guile-next’).
[...]
>
> The main difficulty is that upstream build systems and some of our
> recipes hard-code “/2.0” in the name of
Hello!
The Guile 2.2 series is becoming a reality, so time has come to provide
packages built with/for Guile 2.2 (aka. 2.1, aka. ‘guile-next’).
Commit 947a5d47a50252cb0b87b78a8f83f274dec593e2 adds a
‘package-for-guile-2.2’ procedure similar in spirit to
‘package-with-python2’. It provides a simp
