From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: guile-next: Set correct native search paths.
Date: Mon, 22 Feb 2016 00:11:30 +0100 [thread overview]
Message-ID: <87k2lx3bh9.fsf@drakenvlieg.flower> (raw)
In-Reply-To: <871t8ez7g6.fsf@igalia.com> (Andy Wingo's message of "Mon, 15 Feb 2016 09:47:05 +0100")
Andy Wingo writes:
>> + (native-search-paths
>> + (list (search-path-specification
>> + (variable "GUILE_LOAD_PATH")
>> + (files '("share/guile/site/2.2")))
>> + (search-path-specification
>> + (variable "GUILE_LOAD_COMPILED_PATH")
>> + (files '("lib/guile/2.0/ccache"
>> + "share/guile/site/2.2")))))))
>>
>> (define-public guile-for-guile-emacs
>> (package (inherit guile-next)
>
> This doesn't look right to me; why is GUILE_LOAD_COMPILED_PATH pointing
> into share? Probably need to update the pointer into lib to use 2.2,
> also.
I'm wondering... Currently when switching environments from guile to
guile-next and back, I found that I need to unset
GUILE_LOAD_COMPILED_PATH; otherwise it gets appended to and that breaks.
Why is the `2.0' and `2.2' part of the GUILE_LOAD_COMPILED_PATH? If
guile would always append that (or also look in the directory with
MAJOR.MINOR appended), i.e. something like
lib/guile/ccache # GUILE_LOAD_COMPILED_PATH
lib/guile/ccache/2.0 # guile-2.0 appends 2.0
lib/guile/ccache/2.2 # guile-2.2 appends 2.2
wouldn't that help a lot with picking up the right .go files when
running different versions of guile?
Greetings, Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2016-02-21 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 5:13 [PATCH] gnu: guile-next: Set correct native search paths Thompson, David
2016-02-13 7:25 ` Jan Nieuwenhuizen
2016-02-15 8:47 ` Andy Wingo
2016-02-15 13:04 ` Thompson, David
2016-02-21 23:11 ` Jan Nieuwenhuizen [this message]
2016-02-24 0:42 ` Thompson, David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2lx3bh9.fsf@drakenvlieg.flower \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).