From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 2/4] e2fsprogs: build shared library for the host
Date: Wed, 22 Aug 2018 13:46:51 +0200 [thread overview]
Message-ID: <20180822134651.64f35c4c@windsurf> (raw)
In-Reply-To: <20180821221141.GU15347@scaer>
Hello,
On Wed, 22 Aug 2018 00:11:41 +0200, Yann E. MORIN wrote:
> I lknow this is not your fault, but I find it more readable when the
> --disable are all grouped together, and the --enable ones as well.
>
> It also helps spot potentialy issues when the ordering is the same btw
> host and target variants.
I have pushed an additional commit fixing this for the host configure
options.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-22 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 21:59 [Buildroot] [PATCH next 0/4] btrfs-progs related improvements Thomas Petazzoni
2018-08-21 21:59 ` [Buildroot] [PATCH next 1/4] lzo: build shared library for the host Thomas Petazzoni
2018-08-21 22:07 ` Yann E. MORIN
2018-08-21 21:59 ` [Buildroot] [PATCH next 2/4] e2fsprogs: " Thomas Petazzoni
2018-08-21 22:11 ` Yann E. MORIN
2018-08-22 11:46 ` Thomas Petazzoni [this message]
2018-08-21 21:59 ` [Buildroot] [PATCH next 3/4] btrfs-progs: drop dependency on e2fsprogs by not building btrfs-convert Thomas Petazzoni
2018-08-21 22:15 ` Yann E. MORIN
2018-08-21 21:59 ` [Buildroot] [PATCH next 4/4] btrfs-progs: make e2fsprogs an optional dependency Thomas Petazzoni
2018-08-21 22:18 ` Yann E. MORIN
2018-08-21 22:08 ` [Buildroot] [PATCH next 0/4] btrfs-progs related improvements Yann E. MORIN
2018-08-22 11:46 ` Thomas Petazzoni
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=20180822134651.64f35c4c@windsurf \
--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