From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] boot/systemd-boot: new package
Date: Wed, 26 Dec 2018 14:59:41 +0100 [thread overview]
Message-ID: <20181226145941.7db5c114@windsurf.home> (raw)
In-Reply-To: <20181226121856.GG14286@scaer>
Hello,
On Wed, 26 Dec 2018 13:18:56 +0100, Yann E. MORIN wrote:
> On 2018-12-26 05:33 -0600, James Hilliard spake thusly:
> > On Wed, Dec 26, 2018 at 2:51 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > > On 2018-12-26 07:56 +0800, james.hilliard1 at gmail.com spake thusly:
> > > > - remove more dependencies checks
> > > Why? That was absolutely not necessary.
> > Hmm, maybe my test setup is different than yours, it seemed to be
> > neccesary to get a succesful compile. My setup where I was getting a
> > failure was default everything other than adding the systemd-boot
> > package .
>
> Hm.. I only tested four setups:
>
> - x86_64, systemd with systemd-boot, external toolchain,
> - x86_64, systemd-boot standalone, external toolchain,
> - i686, systemd with systemd-boot, external toolchain,
> - i686, systemd-boot standalone, external toolchain.
Did you collect these as tests for support/testing/ ? :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-26 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 23:56 [Buildroot] [PATCH v2 1/2] package/systemd: enable building of systemd-boot james.hilliard1 at gmail.com
2018-12-25 23:56 ` [Buildroot] [PATCH v2 2/2] boot/systemd-boot: new package james.hilliard1 at gmail.com
2018-12-26 8:51 ` Yann E. MORIN
2018-12-26 11:33 ` James Hilliard
2018-12-26 12:18 ` Yann E. MORIN
2018-12-26 13:59 ` Thomas Petazzoni [this message]
2018-12-26 18:35 ` Yann E. MORIN
2018-12-26 21:41 ` James Hilliard
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=20181226145941.7db5c114@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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