Efraim Flashner <efr...@flashner.co.il> writes:
> On Sun, 28 Feb 2016 20:44:33 +0100
> Ricardo Wurmus <rek...@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
