From: Maxime Devos <maximedevos@telenet.be>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>, 49565@debbugs.gnu.org
Subject: [bug#49565] [PATCH] gnu: glibc-headers-mesboot: Use %build-inputs in setenv phase
Date: Thu, 15 Jul 2021 18:00:41 +0200 [thread overview]
Message-ID: <b01a587c2b7bf584beac14f3b9ce97765fd24c94.camel@telenet.be> (raw)
In-Reply-To: <4491449.dtmGtMj3lj@popigai>
[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]
> [...]
>
> > As "libc" currently doesn't exist in 'inputs', that means "libc"
> > is searched for in 'native-inputs', which is probably not what you want,
> > given that you are cross-compiling?
>
> Are you saying that ‘%build-inputs’ is the union of ‘inputs’ and ‘native-
> inputs’? For my own education, do you know where that happens?
>
> The manual and the doc string for ‘build-expression->derivation’ only
> mention that it comes from ‘inputs’. I can send a patch to correct them.
I thought "build-expression->derivation" doesn't define %build-inputs
anymore, but apparently it does. However, note that, on core-updates
at least, gnu-build and gnu-cross-build don't use build-expression->derivation,
instead they use gexp->derivation (see (guix build-system gnu)), and gexp->derivation
doesn't define %build-inputs.
gexp->derivation doesn't define %build-inputs, but gnu-build and gnu-cross-build
do:
;; also see with-build-variables
(define %build-host-inputs
#+(input-tuples->gexp build-inputs))
(define %build-target-inputs
(append #$(input-tuples->gexp host-inputs)
#+(input-tuples->gexp target-inputs)))
(define %build-inputs
(append %build-host-inputs %build-target-inputs))
;; ^ the unio native-inputs, inputs and implicit inputs!
(define %outputs
#$(outputs->gexp outputs))
I'm not familiar with 'host-inputs', 'build-inputs' and 'target-inputs'.
They are a ‘bag’ thing, not a ‘package’ thing. You'll have to look at
'lower' to see how native-inputs and inputs are mapped to host-inputs,
build-inputs and target-inuts.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-15 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 0:46 [bug#49565] [PATCH] gnu: glibc-headers-mesboot: Use %build-inputs in setenv phase Thiago Jung Bauermann via Guix-patches via
2021-07-15 2:04 ` Thiago Jung Bauermann via Guix-patches via
2021-07-15 12:58 ` Maxime Devos
2021-07-15 15:03 ` Thiago Jung Bauermann via Guix-patches via
2021-07-15 16:00 ` Maxime Devos [this message]
2021-07-15 17:02 ` Thiago Jung Bauermann via Guix-patches via
2021-07-16 1:31 ` [bug#49565] [PATCH core-updates] gnu: bootstrap: Use %current-target-system to decide bootstrap path Thiago Jung Bauermann via Guix-patches via
2021-07-16 8:20 ` Maxime Devos
2021-07-16 20:01 ` Thiago Jung Bauermann via Guix-patches via
2021-07-18 16:10 ` Maxime Devos
2021-07-18 16:45 ` Thiago Jung Bauermann via Guix-patches via
2021-07-20 0:01 ` [bug#49565] [PATCH core-updates v2] " Thiago Jung Bauermann via Guix-patches via
2021-07-20 13:16 ` Thiago Jung Bauermann via Guix-patches via
2021-07-21 20:30 ` Thiago Jung Bauermann via Guix-patches via
2021-07-21 22:01 ` [bug#49565] [PATCH] gnu: glibc-headers-mesboot: Use %build-inputs in setenv phase Ludovic Courtès
2021-07-22 0:32 ` Thiago Jung Bauermann via Guix-patches via
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=b01a587c2b7bf584beac14f3b9ce97765fd24c94.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49565@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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).