From: "Paul A. Patience" <paul@apatience.com>
To: Robby Zambito <contact@robbyzambito.me>
Cc: 50084@debbugs.gnu.org
Subject: [bug#50084] [PATCH v3] gnu: waypipe: Clean up phases and dependencies.
Date: Thu, 19 Aug 2021 04:04:27 +0000 [thread overview]
Message-ID: <0_3aaZdQOyW0x0cY_qfhu-GiM_BUiQzfo2SH3bQ6rSo0r5t2tl980g9DPYC2S9QFEcRnB_U9CiQp1qoZHkQ_kqxSS1OIBTHNJTmE4S1oCaA=@apatience.com> (raw)
In-Reply-To: <20210819020234.642522-1-contact@robbyzambito.me>
On Wednesday, August 18th, 2021 at 22:02, Robby Zambito <contact@robbyzambito.me> wrote:
> I'm a bit confused as to why test dependencies are supposed to be
> native-inputs. Aren't the tests run on the target architecture, not the
> build machine architecture? And aren't native-inputs built for the build
> machine architecture?
You might be right.
I haven't yet done any cross compiling with Guix yet, so I don't know much about it.
I'll have to let someone with more knowledge comment on this.
Best regards,
Paul
next prev parent reply other threads:[~2021-08-19 4:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 1:53 [bug#50084] [PATCH] gnu: Add waypipe Robby Zambito
2021-08-18 20:27 ` [bug#50084] [PATCH v2] gnu: waypipe: Enable tests Robby Zambito
2021-08-19 2:02 ` [bug#50084] [PATCH v3] gnu: waypipe: Clean up phases and dependencies Robby Zambito
2021-08-19 4:04 ` Paul A. Patience [this message]
2021-08-19 15:24 ` Maxime Devos
2021-08-19 19:58 ` Robby Zambito
2021-08-19 21:13 ` Maxime Devos
2021-08-18 22:56 ` [bug#50084] [PATCH] gnu: Add waypipe Paul A. Patience
2021-08-19 22:11 ` [bug#50084] [PATCH v3] gnu: waypipe: Clean up phases and dependencies Robby Zambito
2021-08-30 1:54 ` [bug#50084] [PATCH] gnu: Add waypipe Robby Zambito
2021-08-30 1:58 ` Robby Zambito
2021-09-06 9:15 ` bug#50084: " Nicolas Goaziou
2021-09-07 21:13 ` [bug#50084] " Maxime Devos
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='0_3aaZdQOyW0x0cY_qfhu-GiM_BUiQzfo2SH3bQ6rSo0r5t2tl980g9DPYC2S9QFEcRnB_U9CiQp1qoZHkQ_kqxSS1OIBTHNJTmE4S1oCaA=@apatience.com' \
--to=paul@apatience.com \
--cc=50084@debbugs.gnu.org \
--cc=contact@robbyzambito.me \
/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).