Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Grzegorz Blach <grzegorz@blach.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/f2fs-tools: fix build with lz4 1.9.4
Date: Tue, 08 Nov 2022 21:22:12 +0100	[thread overview]
Message-ID: <877d05gpsb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221029170023.219493-2-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 29 Oct 2022 19:00:23 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Fix the following build failure raised since bump of lz4 to version
 > 1.9.4 in commit 1f54af8c4f814bfc0993756b82575ad581ce5318:

 > compress.c: In function 'lz4_compress_init':
 > compress.c:36:42: error: 'LZ4_STREAMSIZE_U64' undeclared (first use in this function); did you mean 'LZ4_STREAMSIZE'?
 >    36 | #define LZ4_STREAMSIZE                  (LZ4_STREAMSIZE_U64 * sizeof(long long))
 >       |                                          ^~~~~~~~~~~~~~~~~~

 > Fixes:
 >  - http://autobuild.buildroot.org/results/ca8b6646322a4cb911fad5fb9cb38046743609bf

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2022.08.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-08 20:22 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 [this message]
2022-10-30 10:52 ` [Buildroot] [PATCH 1/2] package/f2fs-tools: add lz4 and lzo optional dependencies Thomas Petazzoni via buildroot
2022-11-08 20:22 ` 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=877d05gpsb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=grzegorz@blach.pl \
    /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