From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Grzegorz Blach <grzegorz@blach.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/f2fs-tools: add lz4 and lzo optional dependencies
Date: Sun, 30 Oct 2022 11:52:05 +0100 [thread overview]
Message-ID: <20221030115205.0fab7010@windsurf> (raw)
In-Reply-To: <20221029170023.219493-1-fontaine.fabrice@gmail.com>
On Sat, 29 Oct 2022 19:00:22 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> lz4 and lzo are optional dependencies (enabled by default) since bump to
> version 1.14.0 in commit cf566658f28f3e4b362cc8f9235e6b7768af355c and
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?id=b585244e726c1024f7b842033689992a383808cc
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...1-configure-ac-fix-cross-compilation.patch | 88 +++++++++++++++++++
> package/f2fs-tools/f2fs-tools.mk | 18 +++-
> 2 files changed, 105 insertions(+), 1 deletion(-)
> create mode 100644 package/f2fs-tools/0001-configure-ac-fix-cross-compilation.patch
Both applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-30 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 17:00 [Buildroot] [PATCH 1/2] package/f2fs-tools: add lz4 and lzo optional dependencies Fabrice Fontaine
2022-10-29 17:00 ` [Buildroot] [PATCH 2/2] package/f2fs-tools: fix build with lz4 1.9.4 Fabrice Fontaine
2022-11-08 20:22 ` Peter Korsgaard
2022-10-30 10:52 ` Thomas Petazzoni via buildroot [this message]
2022-11-08 20:22 ` [Buildroot] [PATCH 1/2] package/f2fs-tools: add lz4 and lzo optional dependencies Peter Korsgaard
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=20221030115205.0fab7010@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=grzegorz@blach.pl \
--cc=thomas.petazzoni@bootlin.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.
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.