From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libostree: needs headers >= 5.8
Date: Fri, 12 Jan 2024 19:42:30 +0100 [thread overview]
Message-ID: <87y1cuwfzd.fsf@48ers.dk> (raw)
In-Reply-To: <20240105181207.748233-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 5 Jan 2024 19:12:07 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> libostree unconditionally uses loop_config since bump to version 2023.5
> in commit c64a3e9767757f6bab0ecf2df35871508003f39e and
> https://github.com/containers/composefs/commit/d7f24100c932cd0da9c315de7c7d44fe7a5005cd
> which is only available with kernel >= 5.8 and
> https://github.com/torvalds/linux/commit/3448914e8cc550ba792d4ccc74471d1ca4293aae
> resulting in the following build failure:
> composefs/libcomposefs/lcfs-mount.c: In function 'setup_loopback':
> composefs/libcomposefs/lcfs-mount.c:273:16: error: variable 'loopconfig' has initializer but incomplete type
> 273 | struct loop_config loopconfig = { 0 };
> | ^~~~~~~~~~~
> Fixes:
> - http://autobuild.buildroot.org/results/25d9d4f256861628ddd8e8ce659a39655d27b457
> - http://autobuild.buildroot.org/results/5c7e1e47c6eb43f7832ef7820ec2b5ac0f3c3696
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-12 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 18:12 [Buildroot] [PATCH 1/1] package/libostree: needs headers >= 5.8 Fabrice Fontaine
2024-01-06 9:50 ` Thomas Petazzoni via buildroot
2024-01-12 18:42 ` Peter Korsgaard [this message]
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=87y1cuwfzd.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=marcus.folkesson@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox