From: Vincent Legoll <vincent.legoll@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>, mail@cbaines.net
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: native or not
Date: Wed, 1 Apr 2020 00:01:20 +0200 [thread overview]
Message-ID: <CAEwRq=rX3eytcDd4m3ZbXw-j6OxvLvoEdG70GsjZ3_WzitNsfQ@mail.gmail.com> (raw)
In-Reply-To: <87d08svep1.fsf@devup.no>
Hello,
On Tue, Mar 31, 2020 at 3:25 PM Marius Bakke <mbakke@fastmail.com> wrote:
> Unless you are cross-compiling (i.e. guix build --target=foo),
> native-inputs and inputs behave exactly the same; they are simply
> concatenated.
OK, thanks for the clarification.
Christopher, I'm not a web guy, I may take a shot at it, when
my todo list gets emptyish, but don't hold your breath, that
may not happen in this life...
Following this will come the next batch of native-inputs.
Built on x86_64, tried to also target aarch64, but kind of
unconclusive (one stopped at perl, another at mit-krb5...)
I've searched core-updates to avoid duplicating work,
but only after having done it... Got lucky to have only
lost a few minutes on openldap...
The graphviz patch may not be for master as it may
force 2918 packages to be rebuilt. The other ones
should be OK.
Question: should I stay on guix-devel, should I add
guix-patches or should I move to guix-patches for
the following patche series ?
--
Vincent Legoll
next prev parent reply other threads:[~2020-03-31 22:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 23:11 native or not Vincent Legoll
2020-03-30 6:57 ` Mathieu Othacehe
2020-03-30 21:25 ` Vincent Legoll
2020-03-30 22:07 ` Vincent Legoll
2020-03-31 7:45 ` Mathieu Othacehe
2020-03-31 8:02 ` Vincent Legoll
2020-03-31 9:17 ` Vincent Legoll
2020-03-31 17:54 ` Christopher Baines
2020-03-31 7:27 ` Mathieu Othacehe
2020-03-31 9:44 ` Tobias Geerinckx-Rice
2020-03-31 9:51 ` Vincent Legoll
2020-03-31 13:25 ` Marius Bakke
2020-03-31 22:01 ` Vincent Legoll [this message]
2020-03-31 22:04 ` [PATCH 1/6] gnu: cgit: Make some inputs native Vincent Legoll
2020-03-31 22:04 ` [PATCH 2/6] gnu: darktable: " Vincent Legoll
2020-04-01 13:58 ` Mathieu Othacehe
2020-04-01 14:15 ` Tobias Geerinckx-Rice
2020-03-31 22:04 ` [PATCH 3/6] gnu: graphviz: " Vincent Legoll
2020-03-31 22:04 ` [PATCH 4/6] gnu: iwd: " Vincent Legoll
2020-03-31 22:04 ` [PATCH 5/6] gnu: mailutils: " Vincent Legoll
2020-04-01 14:03 ` Mathieu Othacehe
2020-03-31 22:04 ` [PATCH 6/6] gnu: nethack: " Vincent Legoll
2020-04-01 14:06 ` Mathieu Othacehe
2020-03-31 23:07 ` [PATCH 1/6] gnu: cgit: " Tobias Geerinckx-Rice
2020-04-01 13:52 ` Mathieu Othacehe
2020-04-01 14:13 ` Tobias Geerinckx-Rice
2020-04-01 14:20 ` Mathieu Othacehe
2020-04-01 17:59 ` Vincent Legoll
2020-04-01 19:23 ` native or not Tobias Geerinckx-Rice
2020-04-01 21:28 ` Vincent Legoll
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=rX3eytcDd4m3ZbXw-j6OxvLvoEdG70GsjZ3_WzitNsfQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=mbakke@fastmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.