> Oh, pity. I can’t help without seeing the code, I’m afraid.
You won't be able to try and reproduce - but at the moment that's a lesser
concern of mine
(you can still see that the module definition itself isn't doing anything
special or unexpected,
but nonetheless, I'll work on getting some code
Stephen Scheck writes:
>> Could you show us your my-module.scm please?
>
> The source is not yet ready for public distribution, so I've elided
> references:
Oh, pity. I can’t help without seeing the code, I’m afraid.
--
Ricardo
> Could you show us your my-module.scm please?
The source is not yet ready for public distribution, so I've elided
references:
(use-modules
((guix licenses) #:prefix license:)
(guix utils)
(guix packages)
(guix git-download)
(guix build-system gnu)
(gnu pac
Hi Stephen,
> When I try to install the package by invoking `guix package -f
> my-module.scm`. Here's the output from the build log:
Could you show us your my-module.scm please?
> make[2]: Nothing to be done for 'install-exec-am'.
> /gnu/store/9kzrrccpzl6i1sfwb0drb00gi2gwk0x0-coreutil
Ricardo,
> I don’t understand this. At what point does it use that Guile? When
> building a package that has “guile” as one of the inputs it is *that*
> variant of Guile that is used. Within the build environment Guix
> doesn’t use any profiles.
When I try to install the package by invoking `g
