From: "(" <paren@disroot.org>
To: "jgart" <jgart@dismail.de>, "Guix Help" <help-guix@gnu.org>
Subject: Re: debugging %build-inputs
Date: Thu, 06 Oct 2022 07:40:31 +0100 [thread overview]
Message-ID: <CNEMV3L8VUGM.2A7GDIKYR3Q71@guix-aspire> (raw)
In-Reply-To: <20221005203508.GC31716@dismail.de>
On Thu Oct 6, 2022 at 2:35 AM BST, jgart wrote:
> (arguments
> `(#:configure-flags
> (list (string-append "--with-tcl="
> (assoc-ref %build-inputs "tcl")
> "/lib") ^^^^^^^^^^^^
> (string-append "--with-tk="
> (assoc-ref %build-inputs "tk")
> "/lib"))))
``%build-inputs'' is an **obsolete** variable that provides an
alist of inputs to output paths:
`(("gcc" . "/gnu/store/...-gcc-...")
("make" . "/gnu/store/...-make-...")
("tcl" . "/gnu/store/...-tcl-...")
("tk" . "/gnu/store/...-tk-..."))
et cetera. So, it should just contain a map of the label of each
input to its compiled store path.
Usage of ``(assoc-ref %build-inputs LABEL)'' is basically the same
as usage of ``#$(this-package-input LABEL)'' or
``#$(this-package-input LABEL)''.
Regarding the debugging question: no, I don't believe there is a
way to start a REPL in the build environment.
-- (
prev parent reply other threads:[~2022-10-06 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 1:35 debugging %build-inputs jgart
2022-10-06 6:40 ` ( [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=CNEMV3L8VUGM.2A7GDIKYR3Q71@guix-aspire \
--to=paren@disroot.org \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.
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).