From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Can the builder access channel code?
Date: Sat, 15 Jun 2019 14:19:49 +0200 [thread overview]
Message-ID: <87imt7hwgq.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87o93mzm4a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
My bad, I had forgotten to add my build-system to the list of build-side modules:
(define %foo-build-system-modules
;; Build-side modules imported by default.
`((my-guix build foo-build-system)
,@%gnu-build-system-modules))
This fixes it, thanks for you help!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-06-15 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 14:02 Can the builder access channel code? Pierre Neidhardt
2019-05-28 14:31 ` Ludovic Courtès
2019-06-15 12:19 ` Pierre Neidhardt [this message]
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=87imt7hwgq.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@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).