From: Ricardo Wurmus <rekado@elephly.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Fix guile-emacs build failure
Date: Sun, 28 Feb 2016 20:58:20 +0100 [thread overview]
Message-ID: <871t7wd2ub.fsf@elephly.net> (raw)
In-Reply-To: <20160228215032.78a4a22a@debian-netbook>
Efraim Flashner <efraim@flashner.co.il> writes:
> 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?
Guile Emacs currently needs to be built with “guile-for-guile-emacs”,
which contains custom patches AFAIU.
Currently the “native-search-path” field is inherited from “guile-next”
and thus contains “2.2” in the paths. This is the reason why Guile
Emacs currently cannot be built.
~~ Ricardo
next prev parent reply other threads:[~2016-02-28 19:58 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
2016-02-28 19:58 ` Ricardo Wurmus [this message]
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
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=871t7wd2ub.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=efraim@flashner.co.il \
--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).