From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Fix guile-emacs build failure
Date: Sun, 28 Feb 2016 21:50:32 +0200 [thread overview]
Message-ID: <20160228215032.78a4a22a@debian-netbook> (raw)
In-Reply-To: <874mcsd3ha.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Sun, 28 Feb 2016 20:44:33 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> @@ -255,7 +256,16 @@ without requiring the source code to be rewritten.")
> ("flex" ,flex)
> ("texinfo" ,texinfo)
> ("gettext" ,gnu-gettext)
> - ,@(package-native-inputs guile-next)))))
> + ,@(package-native-inputs guile-next)))
> + ;; Same as in guile-2.0
> + (native-search-paths
> + (list (search-path-specification
> + (variable "GUILE_LOAD_PATH")
> + (files '("share/guile/site/2.0")))
> + (search-path-specification
> + (variable "GUILE_LOAD_COMPILED_PATH")
> + (files '("lib/guile/2.0/ccache"
> + "share/guile/site/2.0")))))))
>
What happens if you're building it with guile-next? Doesn't the search-path
need to be 2.2 or something similar?
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-28 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 19:44 [PATCH] Fix guile-emacs build failure Ricardo Wurmus
2016-02-28 19:50 ` Efraim Flashner [this message]
2016-02-28 19:58 ` Ricardo Wurmus
2016-03-12 17:47 ` Danny Milosavljevic
2016-03-12 21:17 ` Christopher Allan Webber
2016-03-12 21:42 ` Danny Milosavljevic
2016-03-13 22:05 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160228215032.78a4a22a@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.