From: Andy Wingo <wingo@igalia.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: guile-next: Set correct native search paths.
Date: Mon, 15 Feb 2016 09:47:05 +0100 [thread overview]
Message-ID: <871t8ez7g6.fsf@igalia.com> (raw)
In-Reply-To: <CAJ=RwfYqO4icdGq6OjQCFA7DxHMFoH5C_-XsLy8qWvsGP26NEw@mail.gmail.com> (David Thompson's message of "Sat, 13 Feb 2016 00:13:33 -0500")
On Sat 13 Feb 2016 06:13, "Thompson, David" <dthompson2@worcester.edu> writes:
> diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
> index e6e7228..11d9da1 100644
> --- a/gnu/packages/guile.scm
> +++ b/gnu/packages/guile.scm
> @@ -210,7 +210,15 @@ without requiring the source code to be rewritten.")
> ;; times (almost 3 hours on a 4-core Intel i5).
> (snippet '(for-each delete-file
> (find-files "prebuilt" "\\.go$")))))
> - (synopsis "Snapshot of what will become version 2.2 of GNU Guile")))
> + (synopsis "Snapshot of what will become version 2.2 of GNU Guile")
> + (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.
Andy
next prev parent reply other threads:[~2016-02-15 8:47 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 [this message]
2016-02-15 13:04 ` Thompson, David
2016-02-21 23:11 ` Jan Nieuwenhuizen
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=871t8ez7g6.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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).